[
https://issues.apache.org/jira/browse/HBASE-13885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588624#comment-14588624
]
Andrew Purtell commented on HBASE-13885:
----------------------------------------
bq. do we have too many branches to maintain now?
I don't find this to be the case, but it's going to depend on workflow. I start
with a master patch, then pick back (with adjustments) to branch-1, then pick
back that commit to 1.2, then pick back that commit to 1.1, then 1.0, 0.98 etc.
If we are good with this approach then I think it can work for others. The
number of branches will slow us down, though, that's true. Expect to only
commit one or two things per day. That can have its benefits, actually.
It's fine if you leave off 0.98, I'll take care of that, but leave the fix
version if it's relevant.
> ZK watches leaks during snapshots
> ---------------------------------
>
> Key: HBASE-13885
> URL: https://issues.apache.org/jira/browse/HBASE-13885
> Project: HBase
> Issue Type: Bug
> Components: snapshots
> Affects Versions: 0.98.12
> Reporter: Abhishek Singh Chouhan
> Assignee: Lars Hofhansl
> Priority: Critical
> Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.1, 1.3.0
>
> Attachments: 13885-0.98-v2.txt, 13885-0.98-v3.txt, 13885-master.txt
>
>
> When taking snapshot of a table a watcher over
> /hbase/online-snapshot/abort/snapshot-name is created which is never cleared
> when the snapshot is successful. If we use snapshots to take backups daily we
> accumulate a lot of watches.
> Steps to reproduce -
> 1) Take snapshot of a table - snapshot 'table_1', 'abc'
> 2) Run the following on zk node or alternatively observe zk watches metric
> echo "wchc" | nc localhost 2181
> /hbase/online-snapshot/abort/abc can be found.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
