dlmarion commented on PR #3872: URL: https://github.com/apache/accumulo/pull/3872#issuecomment-1777619044
> @dlmarion would it make sense to remove `ManagementAction.BAD_STATE` and roll it into this new more general error handling? BAD_STATE is set in TabletManagementIterator when `tm.isFutureAndCurrentLocationSet()`. However, it's never checked in TabletGroupWatcher. Instead, TGW also checks `tm.isFutureAndCurrentLocationSet()` and throws `BadLocationStateException` in this case. When this is thrown, `repairMetadata` is called to fix it. I think we can get rid of BAD_STATE in the iterator entirely, as it's checked in TGW. I don't think we should roll it into the error handling. -- 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]
