ivakegg commented on PR #3139: URL: https://github.com/apache/accumulo/pull/3139#issuecomment-1362940768
The problem is that loc is cleared when a tserver is shutdown. So there is nothing preserved that specifies where the tablet was last hosted. Another thought was to set the future location but I feel that can get us into inconsistent states as well. How can the last location denote a dirty shutdown if at the time that happens it may or may not be equivalent to the current location? In our case it really does not matter what tserver was hosting the tablet when the data was written. A good portion of our data is not rewritten and yet the tablet is hosted on a different tserver because of balancing activities. I don't mind using a property to change the semantics of the last location. That would work just as well for us. I will look into doing that. -- 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]
