Support differentiating between static and dynamic resource groups

[ddanielr]

In the past accumulo has tracked dead tservers.

For resource groups that have dynamic scaling workloads, there should be an option to disable this tracking of "dead" servers.

We probably don't want to remove this functionality entirely because there might be a static group of tservers which could have issues and failures for those machines should be tracked.

[dlmarion]

From what I can tell, the logic in LiveTServerSet.checkServer only adds the tablet server to the dead list if the tablet server path in ZooKeeper exists but there is no lock data, or if the instance does not match (like the tserver was restarted at the same host/port location). The ZooKeeper node for the tserver is deleted after 10 minutes if there is no lock data.

This information is only shown on the Monitor. We could add a Monitor property that is a list of resource groups to ignore, then use that when calling DeadServerList.getList to skip dead servers with a matching resource group in the ServiceLockPath.