Skip to content

Conversation

@ankedia
Copy link
Member

@ankedia ankedia commented Dec 17, 2020

Fix for multiple pod restarts during rolling update. In a domain with multiple clusters, previously it was launching multiple roll commands (one for each cluster) during rolling update. With this change, the roll command gets launched only once after all managed servers are started. This change executes the ManagedServerUpAfter step after the servers in all the clusters get started instead of executing it after servers start in each cluster .

…agedServerUpAfterStep is executed after servers in all clusters started.
@rjeberhard rjeberhard merged commit 46a67d7 into release/3.1.1 Dec 17, 2020
rjeberhard added a commit that referenced this pull request Dec 17, 2020
* Prepare for 3.1.1

* OWLS-86552 - Fix for multiple pod restarts during rolling update. ManagedServerUpAfterStep is executed after servers in all clusters started. (#2109)

* Add PR reference

Co-authored-by: Anil Kedia <[email protected]>
@ankedia ankedia deleted the owls-86552-multi-pod-restarts branch December 17, 2020 20:45
rjeberhard added a commit that referenced this pull request Jan 22, 2021
* Prepare for 3.1.1

* OWLS-86552 - Fix for multiple pod restarts during rolling update. ManagedServerUpAfterStep is executed after servers in all clusters started. (#2109)

* Add PR reference

* patch annotation with slashes fix - from PR 2089

* Update versions and release notes

* Missing files

* Restore 3.1.1 chart

* Clarify Docker Hub, Docker Store and remove unnecessary references to Docker

* Build schema

* Fix broken link

* Adjust wording

* Review comments

Co-authored-by: Anil Kedia <[email protected]>
Co-authored-by: anthony_lai <[email protected]>
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.

3 participants