huizhilu opened a new pull request #1812: URL: https://github.com/apache/helix/pull/1812
### Issues - [ ] My PR addresses the following Helix issues and references them in the PR description: Resolves #1811 ### Description - [ ] Here are some details about my PR, including screenshots of any UI changes: After controller sends a freeze message to participant, participant needs to process the freeze message and execute the freeze request. It will mark the live instance as "frozen" internally in memory and in live instance znode. For session change during freeze, handle new session won't do anything, except creating the live instance znode. To unfreeze, if there is session change during the freeze period, state model state will be synced and current states will be carried over. Then live instance status field is removed. ### Tests - [ ] The following tests are written for this issue: To be added. - The following is the result of the "mvn test" command on the appropriate module: ``` 18:54:19,848 [INFO] Tests run: 1271, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4,925.327 s - in TestSuite 18:54:20,365 [INFO] 18:54:20,365 [INFO] Results: 18:54:20,365 [INFO] 18:54:20,366 [INFO] Tests run: 1271, Failures: 0, Errors: 0, Skipped: 0 18:54:20,366 [INFO] 18:54:20,370 [INFO] 18:54:20,370 [INFO] --- jacoco-maven-plugin:0.8.6:report (generate-code-coverage-report) @ helix-core --- 18:54:20,402 [INFO] Loading execution data file /home/hulu/Projects/helix/helix-core/target/jacoco.exec 18:54:20,854 [INFO] Analyzed bundle 'Apache Helix :: Core' with 909 classes 18:54:22,318 [INFO] ------------------------------------------------------------------------ 18:54:22,318 [INFO] BUILD SUCCESS 18:54:22,318 [INFO] ------------------------------------------------------------------------ 18:54:22,320 [INFO] Total time: 01:22 h 18:54:22,320 [INFO] Finished at: 2021-07-06T18:54:22-07:00 18:54:22,320 [INFO] ------------------------------------------------------------------------ ``` ### Changes that Break Backward Compatibility (Optional) - My PR contains changes that break backward compatibility or previous assumptions for certain methods or API. They include: (Consider including all behavior changes for public methods or API. Also include these changes in merge description so that other developers are aware of these changes. This allows them to make relevant code changes in feature branches accounting for the new method/API behavior.) ### Documentation (Optional) - In case of new functionality, my PR adds documentation in the following wiki page: (Link the GitHub wiki you added) ### Commits - My commits all reference appropriate Apache Helix GitHub issues in their subject lines. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 1. Subject is limited to 50 characters (not including Jira issue reference) 1. Subject does not end with a period 1. Subject uses the imperative mood ("add", not "adding") 1. Body wraps at 72 characters 1. Body explains "what" and "why", not "how" ### Code Quality - My diff has been formatted using helix-style.xml (helix-style-intellij.xml if IntelliJ IDE is used) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
