Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

English best practices: Resource management #345

Merged
merged 8 commits into from
Dec 8, 2021

Conversation

Zhbert
Copy link
Member

@Zhbert Zhbert commented Nov 26, 2021

No description provided.

@Zhbert Zhbert added the test website Deploy website to the Test environment label Nov 26, 2021
@Zhbert Zhbert marked this pull request as ready for review November 26, 2021 15:43
@Zhbert Zhbert removed the test website Deploy website to the Test environment label Nov 29, 2021
@alexey-igrychev alexey-igrychev linked an issue Nov 30, 2021 that may be closed by this pull request
3 tasks
@shurup shurup requested a review from kirkonru December 2, 2021 06:57

In practice, the liveness probe is not as widely used as you may have thought. Its purpose is to restart a container if, for example, the application is frozen. However, in real life, such app deadlocks are an exception rather than the rule. If the application demonstrates partial functionality for some reason (e.g., it cannot restore connection to a database after it has been broken), you have to fix that in the application, rather than “inventing” livenessProbe-based workarounds.

> **Общая рекомендация для всех проб:** выставляйте высокий `timeoutSeconds`. Значение по умолчанию в одну секунду — слишком низкое. Особенно критично для `readinessProbe` и `livenessProbe`. Слишком низкий `timeoutSeconds` будет приводить к тому, что при увеличении времени ответов у приложений в Pod'ах (что обычно происходит для всех Pod'ов сразу благодаря балансированию нагрузки с помощью Service) либо перестанет приходить трафик почти во все Pod'ы (readiness), либо, что ещё хуже, начнутся каскадные перезапуски контейнеров (liveness).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no translation here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has already been translated and even published earlier.

@alexey-igrychev alexey-igrychev linked an issue Dec 7, 2021 that may be closed by this pull request
3 tasks
@Zhbert Zhbert added test website Deploy website to the Test environment and removed test website Deploy website to the Test environment labels Dec 8, 2021
@Zhbert Zhbert merged commit b2004a2 into master Dec 8, 2021
@Zhbert Zhbert deleted the english-resource-management branch December 8, 2021 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Translation of the section "Best Practices for deploying"
3 participants