ddanielr opened a new issue, #3138:
URL: https://github.com/apache/accumulo/issues/3138

   **Is your feature request related to a problem? Please describe.**
   
   ***Problem***
   There is an operational situation where a tserver cannot be terminated 
locally (either ssh or physical access) and is causing issues in accumulo. 
   The tserver needs to marked as "Dead" and accumulo will not automatically 
change the tserver state due to operational health checks still passing.
   
   ***Current workaround***
   In situations where an admin cannot ssh into or remotely terminate a failed 
node running tservers, an admin needs to be able to mark the tservers on that 
node as "dead" so accumulo starts reassigning tablets to other tservers. 
    
   Currently this has been handled by getting the active zlock for that 
specific tserver from zookeeper and then running a delete zlock command via the 
zookeeper shell. 
   
   This seems risky and complicated for what should be a simple operation. 
   
   **Describe the solution you'd like**
   As an Admin, I would like the ability to mark tservers as "dead" via the 
accumulo shell with requiring ssh access to the specific tservers. 
   
   I should be able to do this via a manual accumulo shell command on either a 
per-tserver basis or via a tserver regex to match all tservers against a 
specific node.
   This command should prompt the Admin with a confirmation action and a 
preview list of tservers to mark 'dead'" 
   
   **Describe alternatives you've considered**
   Alternative solution would be increasing the ability for accumulo to detect 
issues with the tservers.
   However this doesn't help with node maintenance actions that may require 
taking tservers offline without ssh access.
   
   **Additional context**
   Add any other context or screenshots about the feature request here.
   


-- 
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: [email protected]

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

Reply via email to