[jira] [Created] (HBASE-20589) Don't need to assign meta to a new RS when standby master become active

Guanghao Zhang created HBASE-20589: -- Summary: Don't need to assign meta to a new RS when standby master become active Key: HBASE-20589 URL: https://issues.apache.org/jira/browse/HBASE-20589 Project:

[jira] [Resolved] (HBASE-20584) TestRestoreSnapshotFromClient failed

[ https://issues.apache.org/jira/browse/HBASE-20584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian resolved HBASE-20584. -- Resolution: Duplicate > TestRestoreSnapshotFromClient failed >

[jira] [Reopened] (HBASE-20564) Tighter ByteBufferKeyValue Cell Comparator

[ https://issues.apache.org/jira/browse/HBASE-20564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reopened HBASE-20564: --- Reopening to fix. Broke stuff (found by [~yuzhih...@gmail.com]) > Tighter ByteBufferKeyValue Cell Comparator >

[jira] [Created] (HBASE-20588) Space quota change after quota violation doesn't seem to take in effect

Biju Nair created HBASE-20588: - Summary: Space quota change after quota violation doesn't seem to take in effect Key: HBASE-20588 URL: https://issues.apache.org/jira/browse/HBASE-20588 Project: HBase

Lots of broken tests on flaky dashboard

I took a look at the flaky dashboard[1] this morning and noticed an alarming number of always failed tests. Is the dashboard still accurate? I know we've moved our unit testing infrastructure around a little bit and wasn't sure if the dashboard needed updates as well. The tests are failing on

[jira] [Created] (HBASE-20587) Remove client-side Jackson dependency

Josh Elser created HBASE-20587: -- Summary: Remove client-side Jackson dependency Key: HBASE-20587 URL: https://issues.apache.org/jira/browse/HBASE-20587 Project: HBase Issue Type: Bug

Re: WAL storage policies and interactions with Hadoop admin tools.

Thanks Sean for the insight & detailed analysis! I think it makes sense to revert HBASE-18118. It's not as trivial to maintain backward compatibility. Kepping "NONE" as the default hsm doesn't harm. Having additional documentation is helpful to avoid confusion (since "NONE" is not a supported

[jira] [Created] (HBASE-20586) SyncTable tool: Add support for cross-realm remote clusters

Wellington Chevreuil created HBASE-20586: Summary: SyncTable tool: Add support for cross-realm remote clusters Key: HBASE-20586 URL: https://issues.apache.org/jira/browse/HBASE-20586 Project:

Re: Accidentally pushed HBASE-19064 as master

I also thought that we have disabled force push on master and other release branches but I tried and succeeded... There are 20+ commits and it is only a few seconds after the accidental push so I just used a force push to revert everything back... 2018-05-15 21:32 GMT+08:00 Sean Busbey

Re: Accidentally pushed HBASE-19064 as master

FYI for those interested I filed INFRA-16532 On Tue, May 15, 2018 at 8:32 AM, Sean Busbey wrote: > In the future please don't do force pushes. I thought we had disabled > them for the master branch. I'll check up with Infra on this. > > Next time just push a revert. > > On

Re: Accidentally pushed HBASE-19064 as master

In the future please don't do force pushes. I thought we had disabled them for the master branch. I'll check up with Infra on this. Next time just push a revert. On Tue, May 15, 2018 at 8:11 AM, 张铎(Duo Zhang) wrote: > Thanks. > > I pushed HBASE-20457 to master and then

[jira] [Created] (HBASE-20585) Need to clear peer map when clearing MasterProcedureScheduler

Duo Zhang created HBASE-20585: - Summary: Need to clear peer map when clearing MasterProcedureScheduler Key: HBASE-20585 URL: https://issues.apache.org/jira/browse/HBASE-20585 Project: HBase

Re: Accidentally pushed HBASE-19064 as master

Thanks. I pushed HBASE-20457 to master and then the Github repo is back to normal... 2018-05-15 19:10 GMT+08:00 Tim Robertson : > Perhaps someone can verify this first: > > // assuming you have ASF upstream of GH (git remote add upstream > git fetch upstream > git

Re: Accidentally pushed HBASE-19064 as master

Perhaps someone can verify this first: // assuming you have ASF upstream of GH (git remote add upstream git fetch upstream git checkout master git reset --hard upstream/master git push origin master --force This should force (i.e. destructive operation) the GH master branch to be the same as

Accidentally pushed HBASE-19064 as master

When committing HBASE-20576... I've done a force push to master immediately and the asf git is back to normal, but the github repo has already been messed up. Does anyone know how to get the github repo back? Really sorry about this...

[jira] [Created] (HBASE-20584) TestRestoreSnapshotFromClient failed

Jingyun Tian created HBASE-20584: Summary: TestRestoreSnapshotFromClient failed Key: HBASE-20584 URL: https://issues.apache.org/jira/browse/HBASE-20584 Project: HBase Issue Type: Bug

Re: [ANNOUNCE] HBaseConAsia 2018 CFP now open!

Yes, it's not available yet but will be soon (as stated in the announcement but probably ignored at a glance) :-) Best Regards, Yu On 15 May 2018 at 14:29, OpenInx wrote: > Hi > > The https://hbase.apache.org/hbaseconasia-2018/ is returning 404 Not > Found > now ... > > On

Re: [ANNOUNCE] HBaseConAsia 2018 CFP now open!

Hi The https://hbase.apache.org/hbaseconasia-2018/ is returning 404 Not Found now ... On Tue, May 15, 2018 at 1:40 PM, Yu Li wrote: > All, > > I'm pleased to announce HBaseConAsia 2018 which is to be held in Beijing, > China on Aug. 17th. > > A call for proposals is