janhoy opened a new pull request #818: SOLR-13672: Zk Status page now parses 
response from Zookeeper 3.5.5 correctly
URL: https://github.com/apache/lucene-solr/pull/818
 
 
   # Description
   
   Admin UI/ZK Status page: Zookeeper 3.5 : 4lw.commands.whitellist error
   Turned out that there is a new line `membership:` in `conf` 4lw response for 
a quorum that does not follow the `key=value` format, so our parsing crashed.
   
   # Solution
   
   * Be more lenient when parsing zk response and disregard the known 
`membership:` line
   * Do not stop parsing when one error occurs, but continue reading response 
from other ZK hosts, gathering up errors in the errors array to display on top
   
   # Tests
   
   Added a new test that mocks the raw response for `ruok`, `mntr` and `conf` 
from zk, so we can test how the handler parses the response and maps them to 
error messages etc.
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to 
Contribute](https://wiki.apache.org/solr/HowToContribute) and my code conforms 
to the standards described there to the best of my ability.
   - [x] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [x] I am authorized to contribute this code to the ASF and have removed 
any code I do not have a license to distribute.
   - [x] I have developed this patch against the `master` branch.
   - [x] I have run `ant precommit` and the appropriate test suite.
   - [x] I have added tests for my changes.
   - [ ] I have added documentation for the Ref Guide (for Solr changes only).

----------------------------------------------------------------
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]


With regards,
Apache Git Services

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

Reply via email to