[jira] [Created] (HBASE-21465) Retry on reportRegionStateTransition can lead to unexpected errors

2018-11-11 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-21465: - Summary: Retry on reportRegionStateTransition can lead to unexpected errors Key: HBASE-21465 URL: https://issues.apache.org/jira/browse/HBASE-21465 Project: HBase

[jira] [Created] (HBASE-21466) WALProcedureStore uses wrong FileSystem if wal.dir is on different FileSystem as rootdir

2018-11-11 Thread Ted Yu (JIRA)
Ted Yu created HBASE-21466: -- Summary: WALProcedureStore uses wrong FileSystem if wal.dir is on different FileSystem as rootdir Key: HBASE-21466 URL: https://issues.apache.org/jira/browse/HBASE-21466

Re: [DISCUSS] Release cadence for HBase 2.y

2018-11-11 Thread Stack
Agree w/ Duo that the 2.x releases have been gated on stability watersheds rather than features. What else do we need to add to HBCK2 Duo (apart from a release)? Related, I was going to work on a 2.0.3 release. It has been a while and a bunch of good stability work has made it into branch-2.0.

Re: [DISCUSS] Release cadence for HBase 2.y

2018-11-11 Thread Allan Yang
But, since that some users may already have their production system on HBase-2.0.x, maybe we should consider their feelings, they are the 'first movers'. If we retire branch-2.0 so quickly, IIRC, the branch-2.0 will be the shortest life branch ever. I think it will hurt the feeling of those 'first

Re: [DISCUSS] Release cadence for HBase 2.y

2018-11-11 Thread Allan Yang
Stack, are you suggest about retiring branch-2.0? I think it is OK, since branch-2.0 is almost the same with branch-2.1 now(except some new feature on replication). Yes, agree that we should help out on branch-2.2. AMv2 changed a lot in branch-2, there may still have some work to do to make

[jira] [Created] (HBASE-21468) separate workers for meta table is not working

2018-11-11 Thread Allan Yang (JIRA)
Allan Yang created HBASE-21468: -- Summary: separate workers for meta table is not working Key: HBASE-21468 URL: https://issues.apache.org/jira/browse/HBASE-21468 Project: HBase Issue Type: Bug

[jira] [Resolved] (HBASE-21423) Procedures for meta table/region should be able to execute in separate workers

2018-11-11 Thread Allan Yang (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allan Yang resolved HBASE-21423. Resolution: Fixed Opened HBASE-21468 for the addendum, close this one > Procedures for meta

Re: [DISCUSS] Release cadence for HBase 2.y

2018-11-11 Thread Stack
Yes. Was suggesting retiring branch-2.0 and suggesting that we throw the troops against the branch-2.2 flank. Agree though that if there are folks who want more releases, lets do them (please speak up if this is so). 2.0.3 will be good since it close to 2.1.1. Unless demand, 2.0.4 will likely

[jira] [Created] (HBASE-21469) Re-visit post* hooks in DDL operations

2018-11-11 Thread Allan Yang (JIRA)
Allan Yang created HBASE-21469: -- Summary: Re-visit post* hooks in DDL operations Key: HBASE-21469 URL: https://issues.apache.org/jira/browse/HBASE-21469 Project: HBase Issue Type: Bug

Re: [DISCUSS] Release cadence for HBase 2.y

2018-11-11 Thread Misty Linville
This makes me wonder if we have, or have a way to get, analytics about the version people are running? It's not great to guess about things like this. We're making a big assumption that our users actually pay attention to user@ or more often dev@ in order to complain about a branch being retired

[jira] [Created] (HBASE-21467) Fix flaky test TestCoprocessorClassLoader.testCleanupOldJars

2018-11-11 Thread OrDTesters (JIRA)
OrDTesters created HBASE-21467: -- Summary: Fix flaky test TestCoprocessorClassLoader.testCleanupOldJars Key: HBASE-21467 URL: https://issues.apache.org/jira/browse/HBASE-21467 Project: HBase