GrantPSpencer opened a new pull request, #3002:
URL: https://github.com/apache/helix/pull/3002

   ### Issues
   
   - [ ] My PR addresses the following Helix issues and references them in the 
PR description:
   fixes #2940 
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI 
changes:
   
   ["Disabling hard constraint level logging for 
cluster:"](https://github.com/apache/helix/blob/9b339b5c8f543479a593ea9747477b065bcf88ab/helix-core/src/main/java/org/apache/helix/controller/rebalancer/waged/constraints/ConstraintBasedAlgorithm.java#L148)
 is printed every time we attempt to find a node for a toBeAssignedReplica as 
part of ConstraintBasedAlgorithm, even if hard constraint level logging is 
already disabled.
   
   This change refactors the constaint logging enabled logic.
   
   ***NOTE***
   The simplest possible change would also be to simply move the statement from 
`log.info` to `log.debug`. I am fine with either approach. 
   
   ### Tests
   
   - [ ] The following tests are written for this issue:
   
   Existing test TestConstraintBasedAlgorithm 
   
   - The following is the result of the "mvn test" command on the appropriate 
module:
   
   ```
   [INFO] -------------------------------------------------------
   [INFO]  T E S T S
   [INFO] -------------------------------------------------------
   [INFO] Running 
org.apache.helix.controller.rebalancer.waged.constraints.TestConstraintBasedAlgorithm
   [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.579 
s - in 
org.apache.helix.controller.rebalancer.waged.constraints.TestConstraintBasedAlgorithm
   [INFO] 
   [INFO] Results:
   [INFO] 
   [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
   [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:
   
   N/A
   
   ### 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: reviews-unsubscr...@helix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@helix.apache.org
For additional commands, e-mail: reviews-h...@helix.apache.org

Reply via email to