[jira] [Created] (HBASE-22697) when RegionServerStoppedException is received, the client should clear meta cache

Junhong Xu created HBASE-22697: -- Summary: when RegionServerStoppedException is received, the client should clear meta cache Key: HBASE-22697 URL: https://issues.apache.org/jira/browse/HBASE-22697 Projec

[jira] [Created] (HBASE-22696) LockProcedure cleanups

stack created HBASE-22696: - Summary: LockProcedure cleanups Key: HBASE-22696 URL: https://issues.apache.org/jira/browse/HBASE-22696 Project: HBase Issue Type: Sub-task Environment: Our Duo m

[jira] [Created] (HBASE-22695) Store the rsgroup of a table in table configuration

Duo Zhang created HBASE-22695: - Summary: Store the rsgroup of a table in table configuration Key: HBASE-22695 URL: https://issues.apache.org/jira/browse/HBASE-22695 Project: HBase Issue Type: Sub

[jira] [Resolved] (HBASE-22694) Use hbase.zookeeper.quorum if fs.hboss.sync.zk.connectionString is not defined

[ https://issues.apache.org/jira/browse/HBASE-22694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved HBASE-22694. Resolution: Fixed Hadoop Flags: Reviewed Tested by hand using the following: {noformat} for

[jira] [Created] (HBASE-22694) Use hbase.zookeeper.quorum if fs.hboss.sync.zk.connectionString is not defined

Josh Elser created HBASE-22694: -- Summary: Use hbase.zookeeper.quorum if fs.hboss.sync.zk.connectionString is not defined Key: HBASE-22694 URL: https://issues.apache.org/jira/browse/HBASE-22694 Project: H

Re: [DISCUSS] What to do with branches for EOL versions

I agree that deleting EOM branches is the best approach (with tags). Having a branch for an EOM line doesn't make sense since a branch signifies (and/or promotes) active development. Having a tag signifies that this line is static and is a point-in-time pointer to the branch. In the worst case scen

[jira] [Resolved] (HBASE-21606) Document use of the meta table load metrics added in HBASE-19722

[ https://issues.apache.org/jira/browse/HBASE-21606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-21606. - Resolution: Fixed Fix Version/s: 2.1.7 1.4.11 2.2.1

Re: [DISCUSS] What to do with branches for EOL versions

I think delete EOM branches and keeping only tags sounds reasonable, but ain't much experienced on releases management, honestly. Do we know what's the standard among most apache projects? Maybe we could follow those? Em seg, 15 de jul de 2019 às 15:27, Josh Elser escreveu: > (Sending this note

[DISCUSS] What to do with branches for EOL versions

(Sending this note for Busbey as he's chasing other stuff) He had sent a note to private asking what had happened to branch-1.2. In my cleanup of old branches to try to reduce our Jenkins usage at the request of Infra, I created a git tag instead of the branch: branch-1.2 was deleted remotely,

[jira] [Resolved] (HBASE-22675) Use commons-cli from hbase-thirdparty

[ https://issues.apache.org/jira/browse/HBASE-22675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved HBASE-22675. Resolution: Fixed Hadoop Flags: Reviewed > Use commons-cli from hbase-thirdparty > -

Re: The pre commit for GitHub PR is broken

Also just to set expectations, the PR checking job might still give you feedback occasionally because it will evaluate ALL open PRs any time a committer goes to the build job and tells it to do a scan. I *think* the feedback it gives when it runs will still be as accurate as normal. On Mon, Jul 1

[jira] [Resolved] (HBASE-22693) snapshot fails with NPE in standalone mode.

[ https://issues.apache.org/jira/browse/HBASE-22693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pankaj Kumar resolved HBASE-22693. -- Resolution: Duplicate > snapshot fails with NPE in standalone mode. >

[jira] [Created] (HBASE-22693) snapshot fails with NPE in standalone mode.

Sanjeet Nishad created HBASE-22693: -- Summary: snapshot fails with NPE in standalone mode. Key: HBASE-22693 URL: https://issues.apache.org/jira/browse/HBASE-22693 Project: HBase Issue Type: B

Re: Backport pre/post Grant/Revoke events to branch-2.1

> Unfortunately upgrading to 2.2 doesn’t seem to be feasible at the moment, thought it would be a straightforward resolution. What's your consideration about upgrading to 2.2 ? Mind to share it ? > My question was about whether it’s possible at all in the current architecture of branch-2.1. Look

Re: Backport pre/post Grant/Revoke events to branch-2.1

Hi OpenInx, I meant RegionObserver, but it doesn’t really matter: your patch implemented it in MasterObserver, but either observer would be fine for us. Unfortunately upgrading to 2.2 doesn’t seem to be feasible at the moment, thought it would be a straightforward resolution. To be more specif

[jira] [Resolved] (HBASE-22414) Interruption of moving regions in RSGroup will cause regions on wrong rs

[ https://issues.apache.org/jira/browse/HBASE-22414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil resolved HBASE-22414. -- Resolution: Fixed Squashed PR commits and pushed to master. Thanks for the con

The pre commit for GitHub PR is broken

The jenkins job can not receive new builds event after July 10 https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/indexing/events Filed https://issues.apache.org/jira/browse/INFRA-18748 for this. Please consider using the old 'Submit Patch' way to run pre commit. Sorry about this.