Skip to content

Conversation

@ddanielr
Copy link
Contributor

Changes the delete action of the shell fate --delete to actually remove the fate transaction id from table_locks instead of looking for the zlock under the manager lock.

This matches the same delete behavior as the admin fate --delete command

Relates to #6044 as this was discovered during attempts to consolidate the server zlock deletion code.

Changes the delete action of the `shell fate --delete` to actually
remove the fate transaction id from table_locks instead of looking for
the zlock under the manager lock.

This matches the same delete behavior as the `admin fate --delete` command
@ddanielr ddanielr added this to the 2.1.5 milestone Jan 12, 2026
@ddanielr ddanielr added the bug This issue has been verified to be a bug. label Jan 12, 2026
@ddanielr
Copy link
Contributor Author

Looking at the code history, I'm not sure if the shell fate --delete actions ever worked correctly since the fate print commands all looked under the /accumulo/<instance_id>/table_locks zk location.

Copy link
Contributor

@keith-turner keith-turner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you try running these changes with a locked fate operation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug This issue has been verified to be a bug.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants