sigram commented on pull request #73:
URL: https://github.com/apache/solr/pull/73#issuecomment-833568922
Thanks all for the comments and suggestions!
--
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
sigram commented on pull request #73:
URL: https://github.com/apache/solr/pull/73#issuecomment-833568542
Merged.
--
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 querie
sigram commented on pull request #73:
URL: https://github.com/apache/solr/pull/73#issuecomment-833363140
@janhoy the 1-50 and 51-99 thresholds make sense to me. I'll change the PR
accordingly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
sigram commented on pull request #73:
URL: https://github.com/apache/solr/pull/73#issuecomment-832721375
Sure, I'll write the docs / CHANGES before merging.
The reason I added ORANGE is that it conveys a much greater sense of urgency
than YELLOW - it's quite possible to temporarily l
sigram commented on pull request #73:
URL: https://github.com/apache/solr/pull/73#issuecomment-832655630
@janhoy I'd like to wrap it up... Changes since your comments:
* no leader is a RED alert
* I agree that 1 out of 3 replicas is serious enough. Of course, the levels
here are arbit
sigram commented on pull request #73:
URL: https://github.com/apache/solr/pull/73#issuecomment-820267238
The idea behind ORANGE was that the state of the collection is critically
degraded - and even though 2/10 replicas are still up, and things are still
kind of working (so the house is no
sigram commented on pull request #73:
URL: https://github.com/apache/solr/pull/73#issuecomment-818027582
@janhoy @thelabdude @HoustonPutman I would appreciate your comments.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
