NealSun96 opened a new pull request #1076:
URL: https://github.com/apache/helix/pull/1076


   ### Issues
   
   - [x] My PR addresses the following Helix issues and references them in the 
PR description:
   
   Fixes #1075
   
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI 
changes:
   
   Previously, the workflow garbage collection logic was removed in fear of 
race conditions (PR: #803 ). As we see value in bringing back workflow garbage 
collection, we are getting rid of the race conditions and bringing back the 
logic. 
   
   Specifically, two items need to be completed:
   1. Avoid direct dependency of garbage collection stage on the cache. We can 
instead deliver the relevant content of the cache into the stage during sync 
time, and use it during async time. This way the race condition with cache is 
no longer an issue. 
   2. We are getting rid of an unnecessary JobConfig write that serves no 
purpose to avoid possible race conditions.  
   
   ### Tests
   
   - [ ] The following is the result of the "mvn test" command on the 
appropriate module:
   ```
   ```
   
   ### Commits
   
   - [x] 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
   
   - [x] 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.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to