ivakegg commented on issue #3668: URL: https://github.com/apache/accumulo/issues/3668#issuecomment-1660199610
Whatever the case is here, there will always be the possibility that the metadata may get updated but the in-memory data files will not. In the case that I have witnessed, the metadata tablet was extremely busy. The result was that the metadata got updated however the socket timed out on the client side and hence the client did not update the in-memory. I am wondering if there is a way in which the tserver can remedy this situation when it is detected. Alternatively, the metadata update is actually the trigger for the tserver to update its in-memory view. Then maybe we can avoid this half-brain scenario. -- 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]
