[
https://issues.apache.org/jira/browse/HBASE-16208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373388#comment-15373388
]
Joseph commented on HBASE-16208:
--------------------------------
So I put up a checkAndPut (v1) version and a refactored check exist then delete
(v2) patches up. I prefer v2 though, because it provides more information about
the owner of the queue and will abort the server if something goes very wrong
with queue ownership changing beneath you.
> Make TableBasedReplicationQueuesImpl check that queue exists before
> attempting to remove it
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-16208
> URL: https://issues.apache.org/jira/browse/HBASE-16208
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
> Reporter: Joseph
> Assignee: Joseph
> Attachments: HBASE-16208-v1.patch, HBASE-16208-v2.patch,
> HBASE-16208.patch
>
>
> Currently calling TableBasedReplicationQueuesImpl.removeQueue(String queueId)
> will cause it to delete the row with the given queue id. Yet this row is not
> created until the first log is registered for the queue. This causes the
> server to abort if we every try to remove a queue that has not had a log
> registered to it yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
