[GitHub] [accumulo] EdColeman edited a comment on issue #1315: Allow user defined health check for tservers

[GitBox <gi...@apache.org>]

EdColeman edited a comment on issue #1315: Allow user defined health check for tservers
URL: https://github.com/apache/accumulo/issues/1315#issuecomment-519589063
 
 
   One method that I have seen is to have a known location on each node (say /service_runtime) and then specific files, identified by file name can indicate if the service can / should be started.  The presence of a /service_runtime/no_accumulo or /service_runtime/no_xxxx is checked in the start scripts used by things like systemd.  The absence of a file is taken as a go.
   
   The presence of a no_xxx files can be a simple as a 0 length file (touch /service_runtime/no_xxxx) but because it is a file it allows for content / descriptions.  So, even more helpful than just a 0 length file is a comment describing why, mabe who and possibly pointing to a trouble ticket) that way, you don't need a lot of detective work to figure out why it was disabled in the first place and if conditions have changed so that it could be safely put back in service.
   
   For example it's pretty clear if you create a no_xxxx file with a comment like "removed from service because disk1 failed." - anyone coming along can see why, check if the disk has fixed itself or magically gotten healthy, remove the file and restart.

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