dlmarion commented on pull request #2329:
URL: https://github.com/apache/accumulo/pull/2329#issuecomment-1028228525
So, there are two issues currently with this:
1. The current logic in DistributedReadWriteLock.WriteLock.tryLock doesn't
handle multiple concurrent fate transactions for the same table. I believe that
I fixed the logic in the method, but it's still possible for multiple fate
transactions to be started on a table and all of them will get cancelled except
the last one.
2. Errors that occur due to the fate transactions being
cancelled/interrupted are not always making it back to the client, leaving the
client in a state where its waiting indefinitely.
I've spent enough time on this trying to get it to work. I'm inclined to
close this without merging it at this point.
--
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]
