You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2019/04/02 15:10:57 UTC

[GitHub] [accumulo] keith-turner commented on issue #1069: TServer in inconsistent state is never removed

keith-turner commented on issue #1069: TServer in inconsistent state is never removed
URL: https://github.com/apache/accumulo/issues/1069#issuecomment-479042498
 
 
   I think automatically killing tserver could be harmful if its not done properly.  Need to handle the following situations to avoid the killing a large percentage of the tservers unnecessarily
   
    * Master can talk to zookeeper but not most tservers temporarily, however clients can still talk to tservers.
    * There is a bad tablet that once loaded causes a tserver to become non-functional.
   
   These are two situations that if not handled properly could cause the master to automatically kill lots of tservers.  When deciding to kill an individual tserver, the state of the entire cluster should be considered and maybe the history of recent kill actions.
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services