{"id":54987,"date":"2020-01-09T00:00:00","date_gmt":"2020-01-08T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery"},"modified":"2020-02-18T14:03:03","modified_gmt":"2020-02-18T11:03:03","slug":"istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","title":{"rendered":"Istio Circuit Breaker: vypneme vadn\u00e9 kontejnery","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Pr\u00e1zdniny skon\u010dily a my se vrac\u00edme s na\u0161\u00edm druh\u00fdm p\u0159\u00edsp\u011bvkem ze s\u00e9rie o Istio Service Mesh.<\/p>\n

\"Istio
\n
\nDne\u0161n\u00ed t\u00e9ma \u2013 Circuit Breaker, co\u017e v elektrick\u00e9 terminologii znamen\u00e1 \u201eautomatick\u00fd vyp\u00edna\u010d\u201c, v b\u011b\u017en\u00e9 \u0159e\u010di \u201eochrann\u00fd automat\u201c. Jen\u017ee v Istio tento automat nevyp\u00edn\u00e1 p\u0159et\u00ed\u017een\u00fd nebo zkratovan\u00fd obvod, ale vadn\u00e9 kontejnery.
\n<\/a><\/noindex><\/p>\n

Jak by to m\u011blo fungovat ide\u00e1ln\u011b<\/h3>\n

\nKdy\u017e jsou mikroservisy \u0159\u00edzeny Kubernetesem, nap\u0159\u00edklad na platform\u011b OpenShift, automaticky se \u0161k\u00e1luj\u00ed nahoru a dol\u016f podle zat\u00ed\u017een\u00ed. Proto\u017ee mikroservisy b\u011b\u017e\u00ed v podech, m\u016f\u017ee na jednom koncov\u00e9m bod\u011b b\u00fdt sou\u010dasn\u011b n\u011bkolik instanc\u00ed kontejnerizovan\u00e9ho mikroservisu, a Kubernetes bude sm\u011brovat po\u017eadavky a vyva\u017eovat z\u00e1t\u011b\u017e mezi nimi. A \u2013 ide\u00e1ln\u011b \u2013 to v\u0161e by m\u011blo fungovat skv\u011ble.<\/p>\n

Pamatujeme si, \u017ee mikroservisy jsou mal\u00e9 a efem\u00e9rn\u00ed. Efem\u00e9rnost, kter\u00e1 zde znamen\u00e1 jednoduchost vzniku a z\u00e1niku, je \u010dasto podce\u0148ov\u00e1na. Narozen\u00ed a smrt dal\u0161\u00ed instance mikroservisu v pode \u2013 to jsou zcela o\u010dek\u00e1van\u00e9 ud\u00e1losti, OpenShift a Kubernetes s t\u00edm dob\u0159e zach\u00e1zej\u00ed a v\u0161e funguje skv\u011ble \u2013 ale op\u011bt, to je teorie.<\/p>\n

Jak to ve skute\u010dnosti funguje<\/h3>\n

\nA te\u010f si p\u0159edstavte, \u017ee n\u011bkter\u00e1 konkr\u00e9tn\u00ed instance mikroservisu, tedy kontejner, selhala: bu\u010f neodpov\u00edd\u00e1 (chyba 503), nebo \u2013 co\u017e je hor\u0161\u00ed \u2013 reaguje, ale p\u0159\u00edli\u0161 pomalu. Jin\u00fdmi slovy, m\u00e1 probl\u00e9my s odezvou nebo neodpov\u00edd\u00e1 na po\u017eadavky, ale z poolu nen\u00ed automaticky odstran\u011bn. Co s t\u00edmto p\u0159\u00edpadem? Zkusit to znovu? Vy\u0159adit ho z re\u017eimu sm\u011brov\u00e1n\u00ed? A co znamen\u00e1 \u201ep\u0159\u00edli\u0161 pomalu\u201c \u2013 kolik to je v \u010d\u00edslech a kdo je ur\u010duje? Mo\u017en\u00e1 mu jednodu\u0161e d\u00e1t pauzu a zkusit to pozd\u011bji? Pokud ano, tak na jak dlouho?<\/p>\n

Co je to Pool Ejection v Istio<\/h3>\n

\nA tady p\u0159ich\u00e1z\u00ed na pomoc Istio se sv\u00fdmi ochrann\u00fdmi automaty Circuit Breaker, kter\u00e9 do\u010dasn\u011b odstra\u0148uj\u00ed vadn\u00e9 kontejnery z poolu zdroj\u016f sm\u011brov\u00e1n\u00ed a vyva\u017eov\u00e1n\u00ed z\u00e1t\u011b\u017ee, implementuj\u00edce proceduru Pool Ejection.<\/p>\n

Pomoc\u00ed strategie detekce odchylek (outlier detection) Istio detekuje k\u0159iv\u00e9 pode, kter\u00e9 vybo\u010duj\u00ed z norm\u00e1lu, a odstra\u0148uje je z poolu zdroj\u016f na stanovenou dobu, kter\u00e1 se naz\u00fdv\u00e1 \u201espac\u00ed okno\u201c (sleep window). <\/p>\n

Aby uk\u00e1zali, jak to funguje v Kubernetes na platform\u011b OpenShift, za\u010dn\u011bme sn\u00edmkem obrazovky norm\u00e1ln\u011b funguj\u00edc\u00edch mikroslu\u017eeb z p\u0159\u00edkladu v repozit\u00e1\u0159i Red Hat Developer Demos<\/a><\/noindex>. Zde m\u00e1me dv\u011b pod, v1 a v2, p\u0159i\u010dem\u017e v ka\u017ed\u00e9m b\u011b\u017e\u00ed jeden kontejner. Kdy\u017e nejsou pou\u017eita pravidla sm\u011brov\u00e1n\u00ed Istio, Kubernetes ve v\u00fdchoz\u00edm nastaven\u00ed aplikuje vyv\u00e1\u017een\u00e9 cyklick\u00e9 sm\u011brov\u00e1n\u00ed:<\/p>\n

\"Istio<\/p>\n

P\u0159ipravujeme se na selh\u00e1n\u00ed<\/h3>\n

\nNe\u017e provedeme Pool Ejection, mus\u00edme vytvo\u0159it pravidlo sm\u011brov\u00e1n\u00ed Istio. P\u0159edpokl\u00e1dejme, \u017ee chceme distribuovat po\u017eadavky mezi pod podle pom\u011bru 50\/50. Nav\u00edc zv\u00fd\u0161\u00edme po\u010det kontejner\u016f v2 z jednoho na dva, takto:<\/p>\n

oc scale deployment recommendation-v2 --replicas=2 -n tutorial\n<\/code><\/pre>\n
\nNyn\u00ed definujeme pravidlo sm\u011brov\u00e1n\u00ed, aby se provoz rozd\u011bloval mezi pod v pom\u011bru 50\/50.<\/p>\n
\"Istio
\nA zde vypad\u00e1 v\u00fdsledek tohoto pravidla:<\/p>\n
\"Istio
\nM\u016f\u017eeme nam\u00edtnout, \u017ee na tomto sn\u00edmku nen\u00ed 50\/50, ale 14:9, ale \u010dasem se situace uprav\u00ed.<\/p>\n
Vytv\u00e1\u0159\u00edme selh\u00e1n\u00ed<\/h3>\n
\nA nyn\u00ed vy\u0159ad\u00edme jeden ze dvou kontejner\u016f v2, abychom m\u011bli jeden funk\u010dn\u00ed kontejner v1, jeden funk\u010dn\u00ed kontejner v2 a jeden nefunk\u010dn\u00ed kontejner v2: <\/p>\n
\"Istio<\/p>\n
Oprava selh\u00e1n\u00ed<\/h3>\n
\nTak\u017ee m\u00e1me nefunk\u010dn\u00ed kontejner a nastal \u010das na Pool Ejection. S velmi jednoduchou konfigurac\u00ed vylou\u010d\u00edme tento selhan\u00fd kontejner ze v\u0161ech sch\u00e9mat sm\u011brov\u00e1n\u00ed na 15 sekund s o\u010dek\u00e1v\u00e1n\u00edm, \u017ee se vr\u00e1t\u00ed do funk\u010dn\u00edho stavu (bu\u010f se restartuje, nebo obnov\u00ed v\u00fdkon). Takto vypad\u00e1 tato konfigurace a v\u00fdsledky jej\u00edho proveden\u00ed:<\/p>\n
\"Istio
\n\"Istio
\nJak vidno, nefunk\u010dn\u00ed kontejner v2 ji\u017e nen\u00ed pou\u017e\u00edv\u00e1n p\u0159i sm\u011brov\u00e1n\u00ed po\u017eadavk\u016f, proto\u017ee byl odstran\u011bn z poolu. Po uplynut\u00ed 15 sekund se automaticky vr\u00e1t\u00ed do poolu. Vlastn\u011b jsme pr\u00e1v\u011b uk\u00e1zali, jak funguje Pool Ejection.<\/p>\n
Za\u010d\u00edn\u00e1me stav\u011bt architekturu<\/h3>\n
\nPool Ejection v kombinaci s monitorovac\u00edmi schopnostmi Istio umo\u017e\u0148uje za\u010d\u00edt budovat r\u00e1mec automatick\u00e9 v\u00fdm\u011bny nefunk\u010dn\u00edch kontejner\u016f, aby se minimalizovaly, nebo dokonce zcela eliminovaly prostoje a selh\u00e1n\u00ed.
\n\u2003
\nNASA m\u00e1 jedno slavn\u00e9 heslo \u2013 Selh\u00e1n\u00ed nen\u00ed mo\u017enost\u00ed, jeho\u017e autorem je letov\u00fd \u0159editel Gene Kranz<\/a><\/noindex>. Lze to p\u0159elo\u017eit jako \u201ePor\u00e1\u017eka nen\u00ed mo\u017enost\u201c, a smyslem je, \u017ee v\u0161e lze p\u0159im\u011bt k fungov\u00e1n\u00ed, pokud m\u00e1te dostatek v\u016fle. V re\u00e1ln\u00e9m \u017eivot\u011b se v\u0161ak selh\u00e1n\u00ed nevyskytuj\u00ed jen ob\u010das, jsou nevyhnuteln\u00e1, v\u0161ude a ve v\u0161em. Jak se tedy s nimi vypo\u0159\u00e1dat v p\u0159\u00edpad\u011b mikroslu\u017eeb? Z na\u0161eho pohledu je lep\u0161\u00ed spol\u00e9hat se nikoli na s\u00edlu v\u016fle, ale na mo\u017enosti kontejner\u016f. Kubernetes<\/a><\/noindex>, Red Hat OpenShift<\/a><\/noindex>, a Istio<\/a><\/noindex>.<\/p>\n
Jak jsme ji\u017e v\u00fd\u0161e psali, Istio dokonale implementuje osv\u011bd\u010den\u00fd koncept automatick\u00fdch jisti\u010d\u016f. A stejn\u011b jako elektrick\u00fd jisti\u010d odpojuje probl\u00e9movou \u010d\u00e1st obvodu, tak i programov\u00fd Circuit Breaker v Istio p\u0159eru\u0161uje spojen\u00ed mezi tokem po\u017eadavk\u016f a probl\u00e9mov\u00fdm kontejnerem, kdy\u017e je s c\u00edlov\u00fdm bodem n\u011bco v nepo\u0159\u00e1dku, nap\u0159\u00edklad kdy\u017e server spadne nebo za\u010dne zpomalovat.<\/p>\n
A v druh\u00e9m p\u0159\u00edpad\u011b je probl\u00e9m\u016f je\u0161t\u011b v\u00edce, proto\u017ee zpomalen\u00ed jednoho kontejneru nejen\u017ee zp\u016fsobuje kask\u00e1du zpo\u017ed\u011bn\u00ed v obsluhovan\u00fdch slu\u017eb\u00e1ch a t\u00edm sni\u017euje v\u00fdkon syst\u00e9mu jako celku, ale tak\u00e9 vyvol\u00e1v\u00e1 opakovan\u00e9 po\u017eadavky na jinak ji\u017e pomalu funguj\u00edc\u00ed slu\u017ebu, co\u017e situaci jen zhor\u0161uje.<\/p>\n
Circuit Breaker v teorii<\/h3>\n
\nCircuit Breaker je proxy, kter\u00e1 kontroluje tok po\u017eadavk\u016f k c\u00edlov\u00e9mu bodu. Kdy\u017e tento bod p\u0159estane fungovat nebo - v z\u00e1vislosti na nastaven\u00fdch parametrech - za\u010dne zpomalovat, proxy p\u0159eru\u0161\u00ed spojen\u00ed s kontejnerem. Provoz je pot\u00e9 p\u0159esm\u011brov\u00e1n na jin\u00e9 kontejnery, prost\u011b kv\u016fli vyv\u00e1\u017een\u00ed z\u00e1t\u011b\u017ee. Spojen\u00ed z\u016fst\u00e1v\u00e1 otev\u0159en\u00e9 (open) po stanovenou dobu sp\u00e1nku, dejme tomu dv\u011b minuty, a pot\u00e9 se pova\u017euje za polouzav\u0159en\u00e9 (half-open). Pokus o odesl\u00e1n\u00ed dal\u0161\u00edho po\u017eadavku ur\u010duje dal\u0161\u00ed stav spojen\u00ed. Pokud je se slu\u017ebou v\u0161e v po\u0159\u00e1dku, spojen\u00ed se vr\u00e1t\u00ed do pracovn\u00edho stavu a op\u011bt je uzav\u0159eno (closed). Pokud je v\u0161ak se slu\u017ebou st\u00e1le n\u011bco v nepo\u0159\u00e1dku, spojen\u00ed se op\u011bt p\u0159eru\u0161\u00ed a znovu se spou\u0161t\u00ed doba sp\u00e1nku. Takto vypad\u00e1 zjednodu\u0161en\u00fd diagram zm\u011bny stav\u016f Circuit Breakeru:<\/p>\n
\"Istio
\nJe d\u016fle\u017eit\u00e9 poznamenat, \u017ee se to v\u0161echno odehr\u00e1v\u00e1 na \u00farovni, \u0159ekn\u011bme, syst\u00e9mov\u00e9 architektury. Proto v\u00e1s v n\u011bjak\u00e9m okam\u017eiku bude muset nau\u010dit, aby va\u0161e aplikace pracovaly s Circuit Breaker, nap\u0159\u00edklad, aby v odpov\u011bdi poskytly v\u00fdchoz\u00ed hodnotu nebo, pokud je to mo\u017en\u00e9, ignorovaly existenci slu\u017eby. K tomu se pou\u017e\u00edv\u00e1 vzor bulkhead, ale to p\u0159ekra\u010duje r\u00e1mec tohoto \u010dl\u00e1nku.<\/p>\n
Circuit Breaker v praxi<\/h3>\n
\nPro p\u0159\u00edklad spust\u00edme na OpenShift dv\u011b verze na\u0161eho microservisu doporu\u010den\u00ed. Verze 1 bude fungovat norm\u00e1ln\u011b, zat\u00edmco ve verzi 2 implementujeme zpo\u017ed\u011bn\u00ed, abychom napodobili zpo\u017ed\u011bn\u00ed na serveru. K zobrazen\u00ed v\u00fdsledk\u016f pou\u017eijeme n\u00e1stroj siege<\/a><\/noindex>:<\/p>\n
siege -r 2 -c 20 -v customer-tutorial.$(minishift ip).nip.io\n<\/code><\/pre>\n
\n\"Istio
\nV\u0161echno se zd\u00e1 fungovat, ale jakou cenu to m\u00e1? Na prvn\u00ed pohled m\u00e1me 100 % dostupnost, ale pod\u00edvejte se bl\u00ed\u017ee \u2013 maxim\u00e1ln\u00ed doba transakce je cel\u00fdch 12 sekund. To je jasn\u00e9 \u00fazk\u00e9 m\u00edsto, kter\u00e9 je t\u0159eba roz\u0161\u00ed\u0159it.<\/p>\n
K tomu pomoc\u00ed Istio vylou\u010d\u00edme p\u0159\u00edstupy k pomal\u00fdm kontejner\u016fm. Takhle vypad\u00e1 p\u0159\u00edslu\u0161n\u00e1 konfigurace s pou\u017eit\u00edm Circuit Breaker:<\/p>\n
\"Istio
\nPosledn\u00ed \u0159\u00e1dek s parametrem httpMaxRequestsPerConnection nazna\u010duje, \u017ee spojen\u00ed by se m\u011blo p\u0159eru\u0161it p\u0159i pokusu vytvo\u0159it dal\u0161\u00ed \u2013 druh\u00e9 \u2013 spojen\u00ed krom\u011b ji\u017e existuj\u00edc\u00edho. Proto\u017ee n\u00e1\u0161 kontejner napodobuje zpomaluj\u00edc\u00ed slu\u017ebu, takov\u00e9 situace budou ob\u010das vznikat, a pak Istio vr\u00e1t\u00ed chybu 503, a co uk\u00e1\u017ee siege:<\/p>\n
\"Istio<\/p>\n
OK, m\u00e1me Circuit Breaker, co d\u00e1l?<\/h3>\n
\nTak\u017ee jsme implementovali automatick\u00e9 odpojen\u00ed, ani\u017e bychom se dotkli zdrojov\u00e9ho k\u00f3du samotn\u00fdch slu\u017eeb. Pou\u017eit\u00edm Circuit Breaker a v\u00fd\u0161e popsan\u00e9ho postupu Pool Ejection m\u016f\u017eeme odstra\u0148ovat ze zdrojov\u00e9ho fondu zpomaluj\u00edc\u00ed kontejnery, dokud se nedostanou do norm\u00e1lu, a kontrolovat jejich stav v ur\u010den\u00fdch intervalech \u2013 v na\u0161em p\u0159\u00edkladu to jsou dv\u011b minuty (parametr sleepWindow).<\/p>\n
V\u0161imn\u011bte si, \u017ee schopnost aplikace reagovat na chybu 503 se st\u00e1le ur\u010duje na \u00farovni jej\u00edho zdrojov\u00e9ho k\u00f3du. Existuje mnoho strategi\u00ed pro pr\u00e1ci s Circuit Breaker, kter\u00e9 se pou\u017e\u00edvaj\u00ed podle situace.<\/p>\n
V dal\u0161\u00edm p\u0159\u00edsp\u011bvku:<\/b> budeme hovo\u0159it o trasov\u00e1n\u00ed a monitorov\u00e1n\u00ed, kter\u00e9 jsou ji\u017e zabudov\u00e1ny nebo je snadn\u00e9 je p\u0159idat do Istio, a tak\u00e9 o tom, jak \u00famysln\u011b zp\u016fsobit chyby v syst\u00e9mu.
\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041f\u0440\u0430\u0437\u0434\u043d\u0438\u043a\u0438 \u0437\u0430\u0432\u0435\u0440\u0448\u0438\u043b\u0438\u0441\u044c, \u0438 \u043c\u044b \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u0435\u043c\u0441\u044f \u0441 \u043d\u0430\u0448\u0438\u043c \u0432\u0442\u043e\u0440\u044b\u043c \u043f\u043e\u0441\u0442\u043e\u043c \u0438\u0437 \u0441\u0435\u0440\u0438\u0438 \u043f\u043e Istio Service Mesh. \u0421\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u044f\u044f \u0442\u0435\u043c\u0430 \u2013 Circuit Breaker, \u0447\u0442\u043e \u0432 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0435 \u043d\u0430 \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0437\u043d\u0430\u0447\u0430\u0435\u0442 \u00ab\u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u0432\u044b\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c\u00bb, \u0432 \u043f\u0440\u043e\u0441\u0442\u043e\u0440\u0435\u0447\u0438\u0438 \u2013 \u00ab\u0430\u0432\u0442\u043e\u043c\u0430\u0442 \u0437\u0430\u0449\u0438\u0442\u044b\u00bb. \u0422\u043e\u043b\u044c\u043a\u043e \u0432 Istio \u044d\u0442\u043e\u0442 \u0430\u0432\u0442\u043e\u043c\u0430\u0442 \u043e\u0442\u043a\u043b\u044e\u0447\u0430\u0435\u0442 \u043d\u0435 \u043a\u043e\u0440\u043e\u0442\u043d\u0443\u0432\u0448\u0443\u044e \u0438\u043b\u0438 \u043f\u0435\u0440\u0435\u0433\u0440\u0443\u0436\u0435\u043d\u043d\u0443\u044e \u0446\u0435\u043f\u044c, \u0430 \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u044b\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b. \u041a\u0430\u043a \u044d\u0442\u043e \u0434\u043e\u043b\u0436\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u0432 \u0438\u0434\u0435\u0430\u043b\u0435 \u041a\u043e\u0433\u0434\u0430 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-54987","post","type-post","status-publish","format-standard","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\udd47Istio Circuit Breaker: deaktivujeme nefunk\u010dn\u00ed kontejnery | ProHoster","description":"Pr\u00e1zdniny skon\u010dily a my se vrac\u00edme s na\u0161\u00edm druh\u00fdm p\u0159\u00edsp\u011bvkem ze s\u00e9rie o Istio Service Mesh.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","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\udd47Istio Circuit Breaker: \u043e\u0442\u043a\u043b\u044e\u0447\u0430\u0435\u043c \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u044b\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b | ProHoster","og:description":"\u041f\u0440\u0430\u0437\u0434\u043d\u0438\u043a\u0438 \u0437\u0430\u0432\u0435\u0440\u0448\u0438\u043b\u0438\u0441\u044c, \u0438 \u043c\u044b \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u0435\u043c\u0441\u044f \u0441 \u043d\u0430\u0448\u0438\u043c \u0432\u0442\u043e\u0440\u044b\u043c \u043f\u043e\u0441\u0442\u043e\u043c \u0438\u0437 \u0441\u0435\u0440\u0438\u0438 \u043f\u043e Istio Service Mesh.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/istio-circuit-breaker-otklyuchaem-neispravnye-kontejnery","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":"2020-01-08T21:00:00+00:00","article:modified_time":"2020-02-18T11:03:03+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"54987","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-01-24 13:26:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:54:34","updated":"2026-01-24 13:26: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\/54987","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=54987"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/54987\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=54987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=54987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=54987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}