Red Hat Bugzilla – Bug 1314564
Scale the EFK pods when changes are made
Last modified: 2017-08-22 18:26:02 EDT
Section Number and Name:
17.4. POST-DEPLOYMENT CONFIGURATION
Describe the issue:
After working with some of the engineers for the EFK stack, it became apparent that when you make changes to any part of the EFK stack (specifically the FluentD or ElasticSearch) you should scale both of these down to zero, make the changes, and then scale them back up to the appropriate numbers, trying to scale FluentD not too long after scaling ElasticSearch.
Suggestions for improvement:
Make a note about this so that anytime changes are made, the appropriate actions are taken.
You can do this by running `oc scale --replicas=0 dc/<ELASTICSEARCH_DC> dc/<FLUENTD_DC> ` and then, after you have made the change (like attach a PVC) you can scale them back up using `oc scale --replicas=# dc/<ELASTICSEARCH_DC>` and `oc scale --replicas=# dc/<FLUENTD_DC>`