{"id":35092,"date":"2019-10-31T22:02:18","date_gmt":"2019-10-31T19:02:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim\/"},"modified":"2019-10-31T22:02:18","modified_gmt":"2019-10-31T19:02:18","slug":"bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","title":{"rendered":"\u201eBitrix24\u201c: \u201eRychle zvednut\u00e9 se nepova\u017euje za spadl\u00e9\u201c","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes m\u00e1 slu\u017eba \u201eBitrix24\u201c tis\u00edce gigabit\u016f provozu, nem\u00e1 ohromn\u00fd park server\u016f (i kdy\u017e jich samoz\u0159ejm\u011b nen\u00ed m\u00e1lo). Ale pro mnoh\u00e9 z\u00e1kazn\u00edky se stal kl\u00ed\u010dov\u00fdm pracovn\u00edm n\u00e1strojem v jejich firm\u00e1ch, je to skute\u010dn\u00e1 aplikace \u017eivotn\u011b d\u016fle\u017eit\u00e1 pro podnik\u00e1n\u00ed. Proto nesm\u00ed selhat \u2014 to prost\u011b nen\u00ed mo\u017en\u00e9. A co kdy\u017e k v\u00fdpadku p\u0159ece jen dojde, ale slu\u017eba se \u201evr\u00e1t\u00ed\u201c tak rychle, \u017ee si toho nikdo ani nev\u0161imne? A jak se poda\u0159\u00ed realizovat p\u0159i tom failover bez ztr\u00e1ty kvality pr\u00e1ce a po\u010dtu klient\u016f? Alexandr Demidov, \u0159editel odd\u011blen\u00ed cloudov\u00fdch slu\u017eeb \u201eBitrix24\u201c, pro n\u00e1\u0161 blog prozradil, jak se za 7 let existence produktu vyvinul syst\u00e9m rezervov\u00e1n\u00ed.<\/p>\n

\"\u201eBitrix24\u201c:
\n<\/a><\/noindex>
\n\u201eSpu\u0161t\u011bn\u00ed \u201eBitrix24\u201c jako SaaS p\u0159ed 7 lety bylo velkou v\u00fdzvou. Nejv\u011bt\u0161\u00ed obt\u00ed\u017e asi spo\u010d\u00edvala v tom, \u017ee p\u0159ed spu\u0161t\u011bn\u00edm pro ve\u0159ejnost jako SaaS existoval tento produkt pouze jako krabicov\u00e9 \u0159e\u0161en\u00ed. Z\u00e1kazn\u00edci si ho u n\u00e1s kupovali, umis\u0165ovali na sv\u00e9 servery, zakl\u00e1dali firemn\u00ed port\u00e1l \u2014 spole\u010dn\u00e9 \u0159e\u0161en\u00ed pro komunikaci zam\u011bstnanc\u016f, ukl\u00e1d\u00e1n\u00ed soubor\u016f, veden\u00ed \u00fakol\u016f, CRM, to cel\u00e9. A v roce 2012 jsme se rozhodli, \u017ee chceme to spustit jako SaaS, administruj\u00edc\u00ed samostatn\u011b, zaji\u0161\u0165uj\u00edc\u00ed odolnost v\u016f\u010di poruch\u00e1m a spolehlivost. Zku\u0161enosti jsme z\u00edskali v pr\u016fb\u011bhu, proto\u017ee do t\u00e9 doby jsme je jednodu\u0161e nem\u011bli \u2014 byli jsme pouze v\u00fdrobci softwaru, ne poskytovateli slu\u017eeb. <\/p>\n

P\u0159i spu\u0161t\u011bn\u00ed slu\u017eby jsme ch\u00e1pali, \u017ee to nejd\u016fle\u017eit\u011bj\u0161\u00ed je zajistit odolnost v\u016f\u010di poruch\u00e1m, spolehlivost a st\u00e1lou dostupnost slu\u017eby, proto\u017ee pokud m\u00e1te b\u011b\u017enou webovou str\u00e1nku, nap\u0159\u00edklad obchod, a ta v\u00e1m spadne a le\u017e\u00ed hodinu \u2014 trp\u00edte jenom vy, ztr\u00e1c\u00edte objedn\u00e1vky, ztr\u00e1c\u00edte z\u00e1kazn\u00edky, ale pro samotn\u00e9ho va\u0161eho klienta \u2014 pro n\u011bj to nen\u00ed tak kritick\u00e9. Je pochopiteln\u011b na\u0161tvan\u00fd, ale p\u016fjde a koup\u00ed na jin\u00e9m webu. Ale pokud se jedn\u00e1 o aplikaci, na kter\u00e9 je postavena cel\u00e1 pr\u00e1ce uvnit\u0159 firmy, komunikace, rozhodov\u00e1n\u00ed, kl\u00ed\u010dov\u00e9 je z\u00edskat d\u016fv\u011bru u\u017eivatel\u016f, tedy je nezklamat a neselh\u00e1vat. Proto\u017ee ve\u0161ker\u00e1 pr\u00e1ce se m\u016f\u017ee zastavit, pokud n\u011bco uvnit\u0159 nebude fungovat.<\/p>\n

Bitrix24 jako SaaS<\/h4>\n

\nPrvn\u00ed prototyp jsme sestavili rok p\u0159ed ve\u0159ejn\u00fdm spu\u0161t\u011bn\u00edm, v roce 2011. Sestavili jsme ho zhruba za t\u00fdden, pod\u00edvali jsme se na n\u011bj a vyzkou\u0161eli \u2013 byl dokonce funk\u010dn\u00ed. To znamen\u00e1, \u017ee bylo mo\u017en\u00e9 p\u0159ej\u00edt na formul\u00e1\u0159, zadat n\u00e1zev port\u00e1lu, nov\u00fd port\u00e1l se rozjel a vytvo\u0159ila se datab\u00e1ze u\u017eivatel\u016f. Pod\u00edvali jsme se na n\u011bj, zhodnotili v z\u00e1sad\u011b produkt, zabalili to a cel\u00fd rok jsme jej d\u00e1le vyv\u00edjeli. Proto\u017ee jsme m\u011bli velk\u00fd \u00fakol: necht\u011bli jsme m\u00edt dv\u011b r\u016fzn\u00e9 k\u00f3dov\u00e9 z\u00e1kladny, necht\u011bli jsme podporovat zvl\u00e1\u0161\u0165 krabicov\u00fd produkt a zvl\u00e1\u0161\u0165 cloudov\u00e1 \u0159e\u0161en\u00ed \u2013 cht\u011bli jsme to v\u0161e realizovat v r\u00e1mci jednoho k\u00f3du. <\/p>\n

\"\u201eBitrix24\u201c:
\n
\nTypick\u00e1 webov\u00e1 aplikace v t\u00e9 dob\u011b \u2013 to je jeden server, na kter\u00e9m b\u011b\u017e\u00ed n\u011bjak\u00fd k\u00f3d php, datab\u00e1ze mysql, soubory se nahr\u00e1vaj\u00ed, dokumenty, obr\u00e1zky se ukl\u00e1daj\u00ed do slo\u017eky upload \u2013 a to je v\u0161echno. Bohu\u017eel, spu\u0161t\u011bn\u00ed kriticky odoln\u00e9ho webov\u00e9ho servisu na tomto nen\u00ed mo\u017en\u00e9. Tam se nepodporuje distribuovan\u00e9 cache, replikace datab\u00e1z\u00ed se nepodporuje. <\/p>\n

Formulovali jsme po\u017eadavky: um\u011bn\u00ed um\u00edstit se na r\u016fzn\u00fdch m\u00edstech, podporovat replikaci, ide\u00e1ln\u011b um\u00edstit do r\u016fzn\u011b geograficky rozlo\u017een\u00fdch datov\u00fdch center. Odd\u011blit logiku produktu a samotn\u00e9 ukl\u00e1d\u00e1n\u00ed dat. Dynamicky um\u011bt \u0161k\u00e1lovat podle z\u00e1t\u011b\u017ee, statiku v\u016fbec vyn\u00e9st. Z t\u011bchto \u00favah vznikly vlastn\u011b po\u017eadavky na produkt, kter\u00fd jsme po cel\u00fd rok vyv\u00edjeli. B\u011bhem t\u00e9to doby jsme ve vznikaj\u00edc\u00ed platform\u011b, kter\u00e1 byla jednotn\u00e1 \u2013 pro krabicov\u00e1 \u0159e\u0161en\u00ed, pro na\u0161i vlastn\u00ed slu\u017ebu \u2013 ud\u011blali podporu t\u011bch v\u011bc\u00ed, kter\u00e9 jsme pot\u0159ebovali. Podporu replikace mysql na \u00farovni produktu: to znamen\u00e1, \u017ee v\u00fdvoj\u00e1\u0159, kter\u00fd p\u00ed\u0161e k\u00f3d \u2013 nep\u0159em\u00fd\u0161l\u00ed, jak budou jeho dotazy rozd\u011blov\u00e1ny, pou\u017e\u00edv\u00e1 na\u0161e api, a my um\u00edme spr\u00e1vn\u011b rozd\u011blovat dotazy na z\u00e1pis a \u010dten\u00ed mezi master a slave. <\/p>\n

Zavedli jsme podporu na \u00farovni produktu r\u016fzn\u00fdch cloudov\u00fdch objektov\u00fdch \u00falo\u017ei\u0161\u0165: google storage, amazon s3 \u2013 plus, podpora open stack swift. Proto to bylo pohodln\u00e9 jak pro n\u00e1s jako slu\u017ebu, tak pro v\u00fdvoj\u00e1\u0159e, kte\u0159\u00ed pracuj\u00ed s krabicov\u00fdm \u0159e\u0161en\u00edm: pokud pou\u017e\u00edvaj\u00ed pouze na\u0161e api pro pr\u00e1ci, nep\u0159em\u00fd\u0161lej\u00ed, kde nakonec bude soubor ulo\u017een, zda lok\u00e1ln\u011b v souborov\u00e9m syst\u00e9mu nebo se dostane do objektov\u00e9ho \u00falo\u017ei\u0161t\u011b.<\/p>\n

Nakonec jsme se okam\u017eit\u011b rozhodli, \u017ee budeme rezervovat na \u00farovni cel\u00e9ho datov\u00e9ho centra. V roce 2012 jsme se pln\u011b spustili na Amazon AWS, proto\u017ee jsme ji\u017e m\u011bli zku\u0161enosti s touto platformou \u2013 na\u0161e vlastn\u00ed webov\u00e9 str\u00e1nky byly tam hostov\u00e1ny. P\u0159itahovalo n\u00e1s, \u017ee v ka\u017ed\u00e9m regionu Amazonu je n\u011bkolik dostupnostn\u00edch z\u00f3n \u2013 v podstat\u011b, (v jejich terminologii) n\u011bkolik datov\u00fdch center, kter\u00e1 jsou v\u00edce \u010di m\u00e9n\u011b nez\u00e1visl\u00e1 a umo\u017e\u0148uj\u00ed n\u00e1m rezervaci na \u00farovni cel\u00e9ho datov\u00e9ho centra: pokud by jedno z nich n\u00e1hle selhalo, datab\u00e1ze se replikuj\u00ed master-master, servery webov\u00fdch aplikac\u00ed jsou rezervov\u00e1ny a statick\u00e9 soubory jsou ulo\u017eeny v objektov\u00e9m \u00falo\u017ei\u0161ti s3. Z\u00e1t\u011b\u017e je vyva\u017eov\u00e1na \u2013 v t\u00e9 dob\u011b pomoc\u00ed amazon elb, ale o n\u011bco pozd\u011bji jsme p\u0159e\u0161li k vlastn\u00edm vyrovn\u00e1va\u010d\u016fm z\u00e1t\u011b\u017ee, proto\u017ee jsme pot\u0159ebovali slo\u017eit\u011bj\u0161\u00ed logiku. <\/p>\n

Co jsme cht\u011bli, to jsme dostali\u2026<\/h4>\n

\nV\u0161echny z\u00e1kladn\u00ed v\u011bci, kter\u00e9 jsme cht\u011bli zajistit \u2013 odolnost samotn\u00fdch server\u016f, webov\u00fdch aplikac\u00ed a datab\u00e1z\u00ed \u2013 fungovaly dob\u0159e. Nejjednodu\u0161\u0161\u00ed sc\u00e9n\u00e1\u0159: pokud n\u00e1m sel\u017ee n\u011bkter\u00e1 z webov\u00fdch aplikac\u00ed, je to prost\u00e9 \u2013 jsou vy\u0159azeny z vyva\u017eov\u00e1n\u00ed. <\/p>\n

\"\u201eBitrix24\u201c:
\n
\nSelh\u00e1vaj\u00edc\u00ed stroje vyva\u017eova\u010d (tehdy to byl amazon elb) s\u00e1m ozna\u010doval jako unhealthy a vyp\u00ednal na n\u011bm rozd\u011blov\u00e1n\u00ed z\u00e1t\u011b\u017ee. Fungoval amazon auto-scaling: kdy\u017e z\u00e1t\u011b\u017e vzrostla, do auto-scalingov\u00e9 skupiny byly p\u0159id\u00e1ny nov\u00e9 stroje a z\u00e1t\u011b\u017e byla rozlo\u017eena na nov\u00e9 stroje \u2013 v\u0161e bylo v po\u0159\u00e1dku. S na\u0161imi vyva\u017eova\u010di z\u00e1t\u011b\u017ee je logika zhruba stejn\u00e1: pokud se n\u011bco stane se serverem aplikac\u00ed, odstran\u00edme z n\u011bj po\u017eadavky, vy\u0159ad\u00edme tyto stroje, spust\u00edme nov\u00e9 a pokra\u010dujeme v pr\u00e1ci. Schematicky se to za v\u0161echny ty roky trochu zm\u011bnilo, ale st\u00e1le to funguje: je to jednoduch\u00e9, srozumiteln\u00e9 a s t\u00edm nejsou \u017e\u00e1dn\u00e9 komplikace. <\/p>\n

Pracujeme po cel\u00e9m sv\u011bt\u011b, vrcholy z\u00e1t\u011b\u017ee u klient\u016f jsou zcela r\u016fzn\u00e9, a logicky bychom m\u011bli m\u00edt mo\u017enost prov\u00e1d\u011bt ur\u010dit\u00e9 servisn\u00ed pr\u00e1ce s jak\u00fdmikoli komponenty na\u0161eho syst\u00e9mu kdykoli \u2013 pro klienty bez pov\u0161imnut\u00ed. Proto m\u00e1me mo\u017enost vypnout datab\u00e1zi a p\u0159erozd\u011blit zat\u00ed\u017een\u00ed na druh\u00e9 datov\u00e9 centrum. <\/p>\n

Jak to v\u0161echno funguje? \u2014 Provoz p\u0159esm\u011brov\u00e1v\u00e1me na funk\u010dn\u00ed datov\u00e9 centrum \u2014 pokud dojde k hav\u00e1rii v datov\u00e9m centru, tak zcela, pokud se jedn\u00e1 o na\u0161e pl\u00e1novan\u00e9 \u00fadr\u017ebov\u00e9 pr\u00e1ce n\u011bjak\u00e9 datab\u00e1ze, p\u0159esm\u011brov\u00e1v\u00e1me \u010d\u00e1st provozu, kter\u00fd obsluhuje tyto klienty, na druh\u00e9 datov\u00e9 centrum, p\u0159i\u010dem\u017e replikace je pozastavena. Pokud pot\u0159ebujeme nov\u00e9 stroje pro webov\u00e9 aplikace vzhledem k n\u00e1r\u016fstu zat\u00ed\u017een\u00ed v druh\u00e9m datov\u00e9m centru, automaticky se spust\u00ed. Pr\u00e1ce kon\u010d\u00ed, replikace se obnov\u00ed a cel\u00fd provoz se vrac\u00ed zp\u011bt. Pokud mus\u00edme prov\u00e9st zrcadlov\u00e9 pr\u00e1ce v druh\u00e9m DC, nap\u0159\u00edklad nainstalovat syst\u00e9mov\u00e9 aktualizace nebo zm\u011bnit nastaven\u00ed v druh\u00e9 datab\u00e1zi, v podstat\u011b opakujeme to sam\u00e9, pouze na druhou stranu. A pokud dojde k hav\u00e1rii, tak d\u011bl\u00e1me v\u0161e jednodu\u0161e: v monitorovac\u00edm syst\u00e9mu pou\u017e\u00edv\u00e1me mechanismus event-handlers. Pokud se n\u00e1m spust\u00ed n\u011bkolik kontrol a stav p\u0159ejde do kritick\u00e9ho, spust\u00ed se tento handler, zpracovatel, kter\u00fd m\u016f\u017ee prov\u00e9st tu \u010di onu logiku. Pro ka\u017edou datab\u00e1zi m\u00e1me definov\u00e1no, kter\u00fd server je pro ni failover, a kam je t\u0159eba p\u0159esm\u011brovat provoz v p\u0159\u00edpad\u011b jej\u00ed nedostupnosti. Historicky jsme vyu\u017e\u00edvali v n\u011bjak\u00e9 podob\u011b nagios nebo jeho forky. V podstat\u011b podobn\u00e9 mechanismy jsou t\u00e9m\u011b\u0159 v ka\u017ed\u00e9m monitorovac\u00edm syst\u00e9mu, n\u011bco slo\u017eit\u011bj\u0161\u00edho zat\u00edm nepou\u017e\u00edv\u00e1me, ale mo\u017en\u00e1 to n\u011bkdy budeme. Aktu\u00e1ln\u011b monitorov\u00e1n\u00ed reaguje na nedostupnost a m\u00e1 mo\u017enost n\u011bco p\u0159esm\u011brovat.<\/p>\n

V\u0161echno jsme rezervovali?<\/h4>\n

\nM\u00e1me mnoho klient\u016f z USA, mnoho klient\u016f z Evropy, mnoho klient\u016f, kte\u0159\u00ed jsou bl\u00ed\u017ee k v\u00fdchodu \u2014 Japonsko, Singapur a tak d\u00e1le. Samoz\u0159ejm\u011b existuje obrovsk\u00fd pod\u00edl klient\u016f v Rusku. To znamen\u00e1, \u017ee pracujeme daleko ne jen v jednom regionu. U\u017eivatel\u00e9 cht\u011bj\u00ed rychlou odezvu, existuj\u00ed po\u017eadavky na dodr\u017eov\u00e1n\u00ed r\u016fzn\u00fdch m\u00edstn\u00edch z\u00e1kon\u016f, a v ka\u017ed\u00e9m regionu m\u00e1me rezervov\u00e1ny dva datov\u00e9 centra, nav\u00edc existuj\u00ed n\u011bjak\u00e9 dal\u0161\u00ed slu\u017eby, kter\u00e9, op\u011bt, je v\u00fdhodn\u00e9 um\u00edstit do jednoho regionu \u2014 pro klienty, kte\u0159\u00ed v tomto regionu pracuj\u00ed. REST handlerov\u00e9, servery autorizace, jsou m\u00e9n\u011b kritick\u00e9 pro pr\u00e1ci klienta jako celku, na nich se lze p\u0159ep\u00ednat s mal\u00fdm p\u0159ijateln\u00fdm zpo\u017ed\u011bn\u00edm, ale nechceme vym\u00fd\u0161let kolo, jak je monitorovat a co s nimi d\u011blat. Proto se co nejv\u00edce sna\u017e\u00edme vyu\u017e\u00edvat ji\u017e existuj\u00edc\u00ed \u0159e\u0161en\u00ed, a ne rozv\u00edjet u sebe n\u011bjakou kompetenci v oblasti dodate\u010dn\u00fdch produkt\u016f. A n\u011bkde prost\u011b pou\u017e\u00edv\u00e1me p\u0159ep\u00edn\u00e1n\u00ed na \u00farovni DNS, p\u0159i\u010dem\u017e \u017eivost slu\u017eby ur\u010dujeme stejn\u00fdm DNS. V Amazonu je slu\u017eba Route 53, ale to nen\u00ed jen DNS, do kter\u00e9ho lze p\u0159idat z\u00e1znamy a je to hotovo \u2014 je mnohem flexibiln\u011bj\u0161\u00ed a pohodln\u011bj\u0161\u00ed. Pomoc\u00ed n\u011bj m\u016f\u017eete vybudovat geo-distribuovan\u00e9 slu\u017eby s geolokacemi, kdy pomoc\u00ed n\u011bj ur\u010dujete, odkud klient p\u0159i\u0161el, a poskytujete mu ur\u010dit\u00e9 z\u00e1znamy \u2014 s jeho pomoc\u00ed m\u016f\u017eete vybudovat failover architektury. Stejn\u00e9 health-checky jsou nastavov\u00e1ny v samotn\u00e9m Route 53, zad\u00e1v\u00e1te endpointy, kter\u00e9 se monitoruj\u00ed, nastavujete metriky, ur\u010dujete, podle jak\u00fdch protokol\u016f ur\u010dovat \u201e\u017eivost\u201c slu\u017eby \u2014 tcp, http, https; nastavujete frekvenci kontrol, ur\u010duj\u00edc\u00ed, zda je slu\u017eba \u017eiv\u00e1, \u010di nikoli. A v samotn\u00e9m DNS zapisujete, co bude prim\u00e1rn\u00ed, co bude sekund\u00e1rn\u00ed, kam se p\u0159epnout, pokud se spust\u00ed health-check uvnit\u0159 Route 53. To v\u0161e lze ud\u011blat i jin\u00fdmi n\u00e1stroji, ale co je na tom pohodln\u00e9 \u2014 nakonfigurujete to jednou a pak v\u016fbec nep\u0159em\u00fd\u0161l\u00edte o tom, jak prob\u00edhaj\u00ed kontroly, jak jde p\u0159ep\u00edn\u00e1n\u00ed: v\u0161echno funguje samo.<\/p>\n

Prvn\u00ed \u201eale\u201c<\/b>: Jak a \u010d\u00edm z\u00e1lohovat samotn\u00fd route 53? Nikdy nev\u00ed\u0161, co se m\u016f\u017ee st\u00e1t. Na\u0161t\u011bst\u00ed jsme se dosud s touto situac\u00ed nesetkali, ale op\u011bt se chyst\u00e1m vypr\u00e1v\u011bt, pro\u010d jsme si mysleli, \u017ee by byla z\u00e1loha p\u0159ece jen dobr\u00fd n\u00e1pad. T\u00edmto si p\u0159edchyst\u00e1v\u00e1me jakousi ochranu. N\u011bkolikr\u00e1t denn\u011b d\u011bl\u00e1me kompletn\u00ed synchronizaci v\u0161ech z\u00f3n, kter\u00e9 m\u00e1me v route 53. API od Amazonu n\u00e1m umo\u017e\u0148uje klidn\u011b je exportovat do JSONu, a m\u00e1me n\u011bkolik z\u00e1lo\u017en\u00edch server\u016f, na kter\u00e9 to p\u0159ev\u00e1d\u00edme, exportujeme ve form\u011b konfigurac\u00ed a m\u00e1me, abych tak \u0159ekl, z\u00e1lo\u017en\u00ed konfiguraci. V p\u0159\u00edpad\u011b pot\u0159eby ji m\u016f\u017eeme rychle manualn\u011b rozbalit, neztrat\u00edme nastaven\u00ed DNS.<\/p>\n

Druh\u00e9 \u201eale\u201c<\/b>: co je\u0161t\u011b v t\u00e9to sestav\u011b nen\u00ed z\u00e1lohov\u00e1no? Samotn\u00fd load balancer! Rozlo\u017een\u00ed klient\u016f podle region\u016f m\u00e1me velmi jednoduch\u00e9. M\u00e1me dom\u00e9ny bitrix24.ru, bitrix24.com, .de \u2013 te\u010f jich m\u00e1me asi 13 r\u016fzn\u00fdch, kter\u00e9 funguj\u00ed v r\u016fzn\u00fdch z\u00f3n\u00e1ch. Do\u0161li jsme k n\u00e1sleduj\u00edc\u00edmu: v ka\u017ed\u00e9m regionu m\u00e1me sv\u00e9 load balancery. Takto je pohodln\u011bj\u0161\u00ed rozd\u011blovat podle region\u016f, v z\u00e1vislosti na tom, jak\u00e1 je kde \u0161pi\u010dkov\u00e1 z\u00e1t\u011b\u017e s\u00edt\u011b. Pokud dojde k selh\u00e1n\u00ed na \u00farovni jednoho load balanceru, jednodu\u0161e se vy\u0159ad\u00ed z provozu a odstran\u00ed z dns. Pokud dojde k n\u011bjak\u00e9mu probl\u00e9mu s celou skupinou load balancer\u016f, pak se z\u00e1lohuj\u00ed na jin\u00fdch m\u00edstech a p\u0159ep\u00edn\u00e1n\u00ed mezi nimi se prov\u00e1d\u00ed pomoc\u00ed stejn\u00e9ho route53, proto\u017ee d\u00edky kr\u00e1tk\u00e9mu ttl p\u0159epnut\u00ed prob\u00edh\u00e1 maxim\u00e1ln\u011b b\u011bhem 2, 3, 5 minut. <\/p>\n

T\u0159et\u00ed \u201eale\u201c<\/b>: co je\u0161t\u011b nen\u00ed z\u00e1lohov\u00e1no? S3, spr\u00e1vn\u011b. Kdy\u017e ukl\u00e1d\u00e1me soubory, kter\u00e9 uchov\u00e1v\u00e1me u u\u017eivatel\u016f v s3, \u2013 opravdu jsme v\u011b\u0159ili, \u017ee je to nepr\u016fst\u0159eln\u00e9 a nen\u00ed t\u0159eba tam nic z\u00e1lohovat. Ale historie ukazuje, \u017ee se v\u011bci d\u011bj\u00ed jinak. Celkov\u011b Amazon popisuje S3 jako z\u00e1kladn\u00ed slu\u017ebu, proto\u017ee Amazon s\u00e1m S3 pou\u017e\u00edv\u00e1 pro ukl\u00e1d\u00e1n\u00ed obraz\u016f stroj\u016f, konfigurac\u00ed, obraz\u016f AMI, snapshot\u016f\u2026 A kdy\u017e S3 sel\u017ee, jak se to jednou stalo za t\u011bch 7 let, co pou\u017e\u00edv\u00e1me bitrix24, t\u00e1hne to za sebou hromadu probl\u00e9m\u016f \u2014 nedostupnost spu\u0161t\u011bn\u00ed virtu\u00e1lek, poruchy v chodu api a tak d\u00e1le. <\/p>\n

A S3 outage can happen \u2014 it has happened before. This is why we arrived at the following scheme: a few years ago, there were no serious public object storage solutions in Russia, and we considered creating something of our own\u2026 Fortunately, we did not start this because we would have gotten bogged down in the expertise we lack and would likely have made mistakes. Now, there are S3-compatible storages offered by Mail.ru, Yandex, and several other providers. Ultimately, we decided that we wanted, firstly, redundancy, and secondly, the ability to work with local copies. For the specific Russian region, we use the Mail.ru Hotbox service, which is API-compatible with S3. We didn't need any major code adjustments within the application, and we implemented the following mechanism: S3 has triggers that activate on the creation\/deletion of objects, Amazon has a service called Lambda \u2014 this is a serverless code execution that runs precisely when certain triggers are activated.<\/p>\n

\"\u201eBitrix24\u201c:
\n
\nWe kept it very simple: if a trigger is activated, we execute code that copies the object to Mail.ru storage. To fully initiate work with local data copies, we also need reverse synchronization so that clients in the Russian segment can work with a storage solution that is closer to them. Mail is about to finish the triggers in their storage \u2014 it will soon be possible to execute reverse synchronization at the infrastructure level, but for now, we are managing it through our own code. If we see that a client uploaded a file, we queue an event at our code level, process it, and perform reverse replication. The downside is that if we perform any operations on our objects outside our product, using some external tools, we won't account for that. Therefore, we are waiting until the triggers at the storage level are available, so that regardless of where the code is executed, the object that comes to us is copied in the other direction. <\/p>\n

Na \u00farovni k\u00f3du m\u00e1me pro ka\u017ed\u00e9ho klienta zaps\u00e1na ob\u011b \u00falo\u017ei\u0161t\u011b: jedno se pova\u017euje za hlavn\u00ed, druh\u00e9 za z\u00e1lo\u017en\u00ed. Pokud je v\u0161e v po\u0159\u00e1dku, pracujeme s t\u00edm \u00falo\u017ei\u0161t\u011bm, kter\u00e9 je n\u00e1m bl\u00ed\u017ee: tedy na\u0161i klienti, kte\u0159\u00ed jsou v Amazonu, pracuj\u00ed s S3, a ti, kte\u0159\u00ed pracuj\u00ed v Rusku, pracuj\u00ed s Hotbox. Pokud se aktivuje vlajka, mus\u00edme p\u0159ipojit failover a p\u0159epneme klienty na jin\u00e9 \u00falo\u017ei\u0161t\u011b. Tuto vlajku m\u016f\u017eeme nastavovat nez\u00e1visle podle region\u016f a m\u016f\u017eeme je tam a zp\u011bt p\u0159ep\u00ednat. V praxi jsme t\u00edmto je\u0161t\u011b nepou\u017e\u00edvali, ale mechanismus jsme p\u0159edpokl\u00e1dali a mysl\u00edme, \u017ee n\u011bkdy v budoucnu budeme pot\u0159ebovat a bude se hodit. Jednou se to u\u017e stalo. <\/p>\n

Ojej, a v\u00e1\u0161 Amazon utekl...<\/h4>\n

\nV leto\u0161n\u00edm dubnu uplyne v\u00fdro\u010d\u00ed od za\u010d\u00e1tku blokac\u00ed Telegramu v Rusku. Nejv\u00edce posti\u017een\u00fd poskytovatel, kter\u00fd na to doplatil, je Amazon. A bohu\u017eel, v\u00edce utrp\u011bly rusk\u00e9 firmy, kter\u00e9 pracovaly pro cel\u00fd sv\u011bt. <\/p>\n

Pokud je firma glob\u00e1ln\u00ed a Rusko je pro ni velmi mal\u00fd segment, 3-5% \u2014 tak \u010di onak, lze jimi ob\u011btovat. <\/p>\n

Pokud jde o ryze ruskou firmu \u2014 jsem si jist, \u017ee je t\u0159eba m\u00edt um\u00edst\u011bn\u00ed lok\u00e1ln\u011b \u2014 prost\u011b to u\u017eivatel\u016fm usnadn\u00ed p\u0159\u00edstup, bude to pohodln\u011bj\u0161\u00ed, rizik bude m\u00e9n\u011b. <\/p>\n

A pokud je to firma, kter\u00e1 pracuje celosv\u011btov\u011b, a m\u00e1 p\u0159ibli\u017en\u011b stejn\u011b klient\u016f z Ruska jako z jin\u00fdch \u010d\u00e1st\u00ed sv\u011bta? Propojen\u00ed segment\u016f je d\u016fle\u017eit\u00e9, a i tak mus\u00ed spolupracovat. <\/p>\n

Na konci b\u0159ezna 2018 Roskomnadzor poslal nejv\u011bt\u0161\u00edm oper\u00e1tor\u016fm dopis, ve kter\u00e9m je informoval, \u017ee pl\u00e1nuj\u00ed zablokovat n\u011bkolik milion\u016f ip adres Amazonu, aby zablokovali... messenger Zello. D\u011bkujeme t\u011bmto poskytovatel\u016fm \u2014 dopis \u00fasp\u011b\u0161n\u011b v\u0161em unikl, a vzniklo pochopen\u00ed, \u017ee propojen\u00ed s Amazonem m\u016f\u017ee selhat. Bylo to v p\u00e1tek, v panice jsme p\u0159ib\u011bhli k koleg\u016fm z servers.ru s slovy: \u201eP\u0159\u00e1tel\u00e9, pot\u0159ebujeme n\u011bkolik server\u016f, kter\u00e9 nebudou v Rusku, nebudou v Amazonu, ale nap\u0159\u00edklad n\u011bkde v Amsterdamu,\u201c abychom m\u011bli mo\u017enost n\u011bjak\u00fdm zp\u016fsobem tam um\u00edstit vlastn\u00ed. vpn<\/a> A proxy pro n\u011bjak\u00e9 endpointy, na kter\u00e9 nem\u00e1me \u017e\u00e1dn\u00fd vliv, nap\u0159\u00edklad endpointy toho sam\u00e9ho S3 \u2014 nelze se pokusit spustit novou slu\u017ebu a z\u00edskat jinou IP, mus\u00edme se tam prost\u011b doru\u010dit. B\u011bhem n\u011bkolika dn\u016f jsme tyto servery nastavili, spustili a v z\u00e1sad\u011b jsme se p\u0159ipravili na moment, kdy za\u010dnou blokace. Je zaj\u00edmav\u00e9, \u017ee RKN, kdy\u017e vid\u011bl povyk a vzr\u016fstaj\u00edc\u00ed paniku, \u0159ekl: \u201eNe, te\u010f nic blokovat nebudeme.\u201c (Ale to a\u017e do chv\u00edle, kdy za\u010dali blokovat Telegram.) Nastavili jsme mo\u017enosti obch\u00e1zen\u00ed a uv\u011bdomili si, \u017ee blok\u00e1da nebyla zavedena, p\u0159esto jsme se to ale nerozb\u00edrali. Tak, pro v\u0161echny p\u0159\u00edpady. <\/p>\n

\"\u201eBitrix24\u201c:
\n
\nA tak v roce 2019 \u017eijeme v podm\u00ednk\u00e1ch blokac\u00ed. V\u010dera v noci jsem se d\u00edval: kolem milionu IP st\u00e1le pokra\u010duje v blokaci. Pravda, Amazon byl t\u00e9m\u011b\u0159 \u00fapln\u011b odblokov\u00e1n, v nejvy\u0161\u0161\u00edm bod\u011b se to dostalo a\u017e na 20 milion\u016f adres\u2026 Celkov\u011b je realita takov\u00e1, \u017ee konektivita, dobr\u00e1 konektivita \u2014 ta nemus\u00ed b\u00fdt. Nar\u00e1z. M\u016f\u017ee chyb\u011bt z technick\u00fdch d\u016fvod\u016f \u2014 po\u017e\u00e1ry, bagry, to v\u0161e. Nebo, jak jsme vid\u011bli, to nen\u00ed \u00fapln\u011b technick\u00e9. Proto n\u011bkdo velk\u00fd a v\u00fdznamn\u00fd, s vlastn\u00edmi AS, m\u016f\u017ee to \u0159\u00eddit jin\u00fdmi cestami \u2014 direct connect a dal\u0161\u00ed v\u011bci ji\u017e na \u00farovni L2. Ale v jednoduch\u00e9m p\u0159\u00edpad\u011b, jako jsme my nebo je\u0161t\u011b men\u0161\u00ed, je dobr\u00e9 m\u00edt rezervaci na \u00farovni server\u016f, kter\u00e9 jsou zprovozn\u011bny n\u011bkde jinde, p\u0159edem nastaven\u00e9 VPN, proxy, s mo\u017enost\u00ed rychle p\u0159ep\u00ednat konfiguraci v t\u011bch segmentech, kter\u00e9 jsou kritick\u00e9 pro va\u0161i konektivitu. To se n\u00e1m opakovan\u011b hodilo, kdy\u017e za\u010daly blokace Amazonu, p\u0159es n\u011bj jsme v nejhor\u0161\u00edm p\u0159\u00edpad\u011b propou\u0161t\u011bli pr\u00e1v\u011b S3 provoz, ale postupn\u011b se to vy\u0159e\u0161ilo.<\/p>\n

A jak rezervovat\u2026 cel\u00e9ho poskytovatele?<\/h4>\n

\nV sou\u010dasnosti nem\u00e1me sc\u00e9n\u00e1\u0159 pro p\u0159\u00edpad v\u00fdpadku cel\u00e9ho Amazonu. Existuje podobn\u00fd sc\u00e9n\u00e1\u0159 pro Rusko. V Rusku jsme byli um\u00edst\u011bni u jednoho poskytovatele, u kter\u00e9ho jsme vyb\u00edrali, aby bylo n\u011bkolik lokalit. P\u0159ed rokem jsme se v\u0161ak setkali s probl\u00e9mem: i kdy\u017e se jedn\u00e1 o dv\u011b datov\u00e1 centra, na \u00farovni konfigurace s\u00edt\u011b poskytovatele mohou vzniknout probl\u00e9my, kter\u00e9 se dotknou obou datov\u00fdch center. M\u016f\u017eeme tak za\u017e\u00edt nedostupnost na obou m\u00edstech. A to se tak\u00e9 stalo. Nakonec jsme p\u0159epracovali na\u0161i intern\u00ed architekturu. Ta se nezm\u011bnila v\u00fdrazn\u011b, ale pro Rusko m\u00e1me nyn\u00ed dv\u011b lokality, kter\u00e9 nejsou u jednoho poskytovatele, ale u dvou r\u016fzn\u00fdch. Pokud u jednoho dojde k n\u011bjak\u00e9mu v\u00fdpadku, m\u016f\u017eeme p\u0159epnout na druh\u00e9ho.<\/p>\n

Hypoteticky zva\u017eujeme pro Amazon mo\u017enost z\u00e1lohov\u00e1n\u00ed na \u00farovni jin\u00e9ho poskytovatele; mo\u017en\u00e1 Google, mo\u017en\u00e1 n\u011bkdo jin\u00fd\u2026 Ale zat\u00edm jsme v praxi zjistili, \u017ee kdy\u017e dojde k hav\u00e1rii na \u00farovni jedn\u00e9 availability z\u00f3ny u Amazonu, hav\u00e1rie na \u00farovni cel\u00e9ho regionu je pom\u011brn\u011b vz\u00e1cn\u00e1. Tak\u017ee teoreticky m\u00e1me p\u0159edstavu, \u017ee bychom mohli vytvo\u0159it z\u00e1lohu \"Amazon \u2013 ne Amazon\", ale v praxi to zat\u00edm neexistuje. <\/p>\n

P\u00e1r slov o automatizaci<\/h4>\n

\nJe automatizace v\u017edy pot\u0159ebn\u00e1? Zde je na m\u00edst\u011b vzpomenout na efekt Dunninga-Krugera. Na ose \"x\" jsou na\u0161e znalosti a zku\u0161enosti, kter\u00e9 z\u00edsk\u00e1v\u00e1me, a na ose \"y\" \u2013 d\u016fv\u011bra v na\u0161e jedn\u00e1n\u00ed. Nejprve nic nev\u00edme a jsme zcela nejist\u00ed. Pot\u00e9 v\u00edme n\u011bco m\u00e1lo a st\u00e1v\u00e1me se mega-sebev\u011bdom\u00fdmi \u2013 to je takzvan\u00fd \"vrchol stupidity\", dob\u0159e ilustrovan\u00fd obr\u00e1zkem \"hloupost a odvaha\". D\u00e1le se ji\u017e n\u011bco nau\u010d\u00edme a jsme p\u0159ipraveni j\u00edt do boje. Pak naraz\u00edme na n\u011bjak\u00e9 mega-z\u00e1va\u017en\u00e9 probl\u00e9my, dostaneme se do \u00fadol\u00ed zoufalstv\u00ed, kdy sice n\u011bco v\u00edme, ale ve skute\u010dnosti toho v\u00edme mnohem m\u00e9n\u011b. Jak nab\u00edr\u00e1me zku\u0161enosti, st\u00e1v\u00e1me se u\u017e sebev\u011bdom\u011bj\u0161\u00edmi.<\/p>\n

\"\u201eBitrix24\u201c:
\n
\nNa\u0161e logika, co se t\u00fd\u010de r\u016fzn\u00fdch automatick\u00fdch p\u0159epnut\u00ed p\u0159i hav\u00e1ri\u00edch, je velmi dob\u0159e pops\u00e1na t\u00edmto grafem. Za\u010dali jsme bez zku\u0161enost\u00ed, prakticky ve\u0161ker\u00e1 pr\u00e1ce se vykon\u00e1vala ru\u010dn\u011b. Pak jsme si uv\u011bdomili, \u017ee m\u016f\u017eeme na v\u0161echno nasadit automatizaci a jakoby sp\u00e1t v klidu. A najednou jsme narazili na velk\u00fd probl\u00e9m: dostali jsme false positive a neust\u00e1le p\u0159ep\u00edn\u00e1me provoz tam a zp\u011bt, i kdy\u017e to ve skute\u010dnosti nebylo nutn\u00e9. To pak naru\u0161ilo replikaci nebo n\u011bco jin\u00e9ho \u2014 a to je ta prav\u00e1 dolina zoufalstv\u00ed. A pak jsme dosp\u011bli k pozn\u00e1n\u00ed, \u017ee na v\u0161echno je pot\u0159eba se d\u00edvat s rozumem. To znamen\u00e1, \u017ee m\u00e1 smysl se spolehnout na automatizaci, ale z\u00e1rove\u0148 p\u0159edv\u00eddat mo\u017enost fale\u0161n\u00e9ho alarmu. Ale! Pokud jsou n\u00e1sledky destruktivn\u00ed, je lep\u0161\u00ed p\u0159enechat to pohotovostn\u00edmu t\u00fdmu, pohotovostn\u00edm in\u017een\u00fdr\u016fm, kte\u0159\u00ed ov\u011b\u0159\u00ed, zajist\u00ed, \u017ee se opravdu jedn\u00e1 o hav\u00e1rii, a provedou nezbytn\u00e9 kroky ru\u010dn\u011b...<\/p>\n

Z\u00e1v\u011br<\/h4>\n

\nZa 7 let jsme pro\u0161li cestou od toho, \u017ee jakmile n\u011bco spadlo, panika, k uv\u011bdom\u011bn\u00ed, \u017ee probl\u00e9m neexistuje, existuj\u00ed jen \u00fakoly, kter\u00e9 je nutn\u00e9 \u2014 a mo\u017en\u00e9 \u2014 vy\u0159e\u0161it. Kdy\u017e stav\u00edte n\u011bjakou slu\u017ebu, pod\u00edvejte se na ni z nadhledu a zhodno\u0165te v\u0161echna rizika, kter\u00e1 mohou nastat. Pokud je vid\u00edte hned, p\u0159edem napl\u00e1nujte z\u00e1lo\u017en\u00ed opat\u0159en\u00ed a mo\u017enost vytvo\u0159en\u00ed odoln\u00e9 infrastruktury, proto\u017ee jak\u00fdkoli bod, kter\u00fd m\u016f\u017ee selhat a v\u00e9st k nefunk\u010dnosti slu\u017eby \u2014 ten to ud\u011bl\u00e1. A i kdy\u017e se v\u00e1m zd\u00e1, \u017ee n\u011bkter\u00e9 prvky infrastruktury ur\u010dit\u011b nesel\u017eou \u2014 jako nap\u0159\u00edklad s3, m\u011bjte na pam\u011bti, \u017ee se tak m\u016f\u017ee st\u00e1t. A alespo\u0148 teoreticky m\u011bjte p\u0159edstavu o tom, co s nimi budete d\u011blat, pokud k n\u011b\u010demu dojde. M\u011bjte pl\u00e1n na \u0159\u00edzen\u00ed rizik. Kdy\u017e p\u0159em\u00fd\u0161l\u00edte o tom, zda v\u0161e d\u011blat automatizovan\u011b nebo ru\u010dn\u011b, zhodno\u0165te rizika: co se stane, kdy\u017e automatizace za\u010dne v\u0161e p\u0159ep\u00ednat \u2014 nevede to k je\u0161t\u011b hor\u0161\u00edmu sc\u00e9n\u00e1\u0159i ne\u017e hav\u00e1rie? Mo\u017en\u00e1 je n\u011bkde pot\u0159eba rozumn\u00fd kompromis mezi pou\u017eit\u00edm automatizace a reakc\u00ed pohotovostn\u00edho in\u017een\u00fdra, kter\u00fd posoud\u00ed skute\u010dn\u00fd stav a pochop\u00ed, zda je t\u0159eba n\u011bco p\u0159ep\u00ednat okam\u017eit\u011b nebo \"ano, ale ne te\u010f\".<\/p>\n

Rozumn\u00fd kompromis mezi perfekcionismem a re\u00e1ln\u00fdmi silami, \u010dasem a pen\u011bzi, kter\u00e9 m\u016f\u017eete investovat do sch\u00e9matu, kter\u00e9 nakonec budete m\u00edt.<\/p>\n

Tento text je dopln\u011bnou a roz\u0161\u00ed\u0159enou verz\u00ed zpr\u00e1vy Alexandra Demidova na konferenci. Uptime den 4<\/a><\/noindex>.<\/i>
\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041d\u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u0434\u0435\u043d\u044c \u0443 \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u00ab\u0411\u0438\u0442\u0440\u0438\u043a\u044124\u00bb \u043d\u0435\u0442 \u0441\u043e\u0442\u0435\u043d \u0433\u0438\u0433\u0430\u0431\u0438\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430, \u043d\u0435\u0442 \u043e\u0433\u0440\u043e\u043c\u043d\u043e\u0433\u043e \u043f\u0430\u0440\u043a\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 (\u0445\u043e\u0442\u044f \u0438 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0445, \u043a\u043e\u043d\u0435\u0447\u043d\u043e, \u043d\u0435\u043c\u0430\u043b\u043e). \u041d\u043e \u0434\u043b\u044f \u043c\u043d\u043e\u0433\u0438\u0445 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u043e\u043d \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u043c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u043e\u043c \u0440\u0430\u0431\u043e\u0442\u044b \u0432 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u044d\u0442\u043e \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0435 business-critical \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 \u043f\u0430\u0434\u0430\u0442\u044c \u2014 \u043d\u0443, \u043d\u0438\u043a\u0430\u043a \u043d\u0435\u043b\u044c\u0437\u044f. \u0410 \u0447\u0442\u043e \u0435\u0441\u043b\u0438 \u043f\u0430\u0434\u0435\u043d\u0438\u0435 \u0432\u0441\u0435-\u0442\u0430\u043a\u0438 \u0441\u043b\u0443\u0447\u0438\u043b\u043e\u0441\u044c, \u043d\u043e \u00ab\u0432\u043e\u0441\u0441\u0442\u0430\u043b\u00bb \u0441\u0435\u0440\u0432\u0438\u0441 \u0442\u0430\u043a \u0431\u044b\u0441\u0442\u0440\u043e, \u0447\u0442\u043e \u043d\u0438\u043a\u0442\u043e \u043d\u0438\u0447\u0435\u0433\u043e \u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26389,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35092","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47\"Bitrix24\": \"Rychle zprovozn\u011bn\u00e9 se nepova\u017euje za havarovan\u00e9\" | ProHoster","description":"V sou\u010dasn\u00e9 dob\u011b slu\u017eba \"Bitrix24\" nem\u00e1 stovky gigabit\u016f provozu, nem\u00e1 obrovsk\u00fd park server\u016f (i kdy\u017e t\u011bch st\u00e1vaj\u00edc\u00edch je samoz\u0159ejm\u011b dost).","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u00ab\u0411\u0438\u0442\u0440\u0438\u043a\u044124\u00bb: \u00ab\u0411\u044b\u0441\u0442\u0440\u043e \u043f\u043e\u0434\u043d\u044f\u0442\u043e\u0435 \u043d\u0435 \u0441\u0447\u0438\u0442\u0430\u0435\u0442\u0441\u044f \u0443\u043f\u0430\u0432\u0448\u0438\u043c\u00bb | ProHoster","og:description":"\u041d\u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u0434\u0435\u043d\u044c \u0443 \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u00ab\u0411\u0438\u0442\u0440\u0438\u043a\u044124\u00bb \u043d\u0435\u0442 \u0441\u043e\u0442\u0435\u043d \u0433\u0438\u0433\u0430\u0431\u0438\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430, \u043d\u0435\u0442 \u043e\u0433\u0440\u043e\u043c\u043d\u043e\u0433\u043e \u043f\u0430\u0440\u043a\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 (\u0445\u043e\u0442\u044f \u0438 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0445, \u043a\u043e\u043d\u0435\u0447\u043d\u043e, \u043d\u0435\u043c\u0430\u043b\u043e).","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/bitriks24-bystro-podnyatoe-ne-schitaetsya-upavshim","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:02:18+00:00","article:modified_time":"2019-10-31T19:02:18+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35092","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-04 14:51:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:10:27","updated":"2026-02-04 14:51:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/35092","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=35092"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/35092\/revisions"}],"predecessor-version":[{"id":156668,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/35092\/revisions\/156668"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/26389"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=35092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=35092"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=35092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}