[jira] [Created] (HBASE-19494) Create simple WALKey filter that can be plugged in on the Replication Sink

2017-12-11 Thread stack (JIRA)
stack created HBASE-19494: - Summary: Create simple WALKey filter that can be plugged in on the Replication Sink Key: HBASE-19494 URL: https://issues.apache.org/jira/browse/HBASE-19494 Project: HBase

[jira] [Created] (HBASE-19493) Make TestWALMonotonicallyIncreasingSeqId also work with AsyncFSWAL

2017-12-11 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-19493: - Summary: Make TestWALMonotonicallyIncreasingSeqId also work with AsyncFSWAL Key: HBASE-19493 URL: https://issues.apache.org/jira/browse/HBASE-19493 Project: HBase

[jira] [Created] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-11 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-19492: -- Summary: Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config Key: HBASE-19492 URL: https://issues.apache.org/jira/browse/HBASE-19492 Pro

Re: Suggestion to speed up precommit - Reduce versions in Hadoop check

2017-12-11 Thread Apekshit Sharma
https://issues.apache.org/jira/browse/HBASE-19489 On Mon, Dec 11, 2017 at 4:30 PM, Josh Elser wrote: > +1 > > > On 12/11/17 7:11 PM, Apekshit Sharma wrote: > >> Oh, btw, here's the little piece of code if anyone want's to analyze more. >> >> Script to collect precommit runs' console text. >> >>

[jira] [Created] (HBASE-19491) Exclude flaky tests from nightly master run

2017-12-11 Thread Appy (JIRA)
Appy created HBASE-19491: Summary: Exclude flaky tests from nightly master run Key: HBASE-19491 URL: https://issues.apache.org/jira/browse/HBASE-19491 Project: HBase Issue Type: Improvement

Suggestion to speed up precommit - Reduce versions in Hadoop check

2017-12-11 Thread Apekshit Sharma
Hi +1 hadoopcheck 52m 1s Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 2.7.4 or 3.0.0-alpha4. Almost 1 hr to check against 10 versions. And it's only going to increase as more 2.6.x, 2.7.x and 3.0.x releases come out. Suggestion here is simple, let's

[jira] [Created] (HBASE-19490) Rare failure in TestRateLimiter

2017-12-11 Thread Andrew Purtell (JIRA)
Andrew Purtell created HBASE-19490: -- Summary: Rare failure in TestRateLimiter Key: HBASE-19490 URL: https://issues.apache.org/jira/browse/HBASE-19490 Project: HBase Issue Type: Bug Affec

[jira] [Created] (HBASE-19489) Check against only the latest maintenance release in pre-commit hadoopcheck.

2017-12-11 Thread Appy (JIRA)
Appy created HBASE-19489: Summary: Check against only the latest maintenance release in pre-commit hadoopcheck. Key: HBASE-19489 URL: https://issues.apache.org/jira/browse/HBASE-19489 Project: HBase

Re: Suggestion to speed up precommit - Reduce versions in Hadoop check

2017-12-11 Thread Ted Yu
bq. check against only the latest maintenance release for each minor version i.e. 2.6.5, 2.7.4 and 3.0.0-alpha4 Makes sense. For hadoop 3, we can build against 3.0.0-beta1 Cheers On Mon, Dec 11, 2017 at 4:11 PM, Apekshit Sharma wrote: > Oh, btw, here's the little piece of code if anyone want'

Re: Suggestion to speed up precommit - Reduce versions in Hadoop check

2017-12-11 Thread Josh Elser
+1 On 12/11/17 7:11 PM, Apekshit Sharma wrote: Oh, btw, here's the little piece of code if anyone want's to analyze more. Script to collect precommit runs' console text. #!/bin/bash for i in `seq 10100 10300`; do wget -a log -O ${i} https://builds.apache.org/job/PreCommit-HBASE-Build/${i}/

Re: Suggestion to speed up precommit - Reduce versions in Hadoop check

2017-12-11 Thread Apekshit Sharma
Oh, btw, here's the little piece of code if anyone want's to analyze more. Script to collect precommit runs' console text. #!/bin/bash for i in `seq 10100 10300`; do wget -a log -O ${i} https://builds.apache.org/job/PreCommit-HBASE-Build/${i}/consoleText done Number of failed runs: grep "| -

[jira] [Created] (HBASE-19488) Remove Unused Code from CollectionUtils

2017-12-11 Thread BELUGA BEHR (JIRA)
BELUGA BEHR created HBASE-19488: --- Summary: Remove Unused Code from CollectionUtils Key: HBASE-19488 URL: https://issues.apache.org/jira/browse/HBASE-19488 Project: HBase Issue Type: Improvement

Re: Moving To SLF4J and Log4J2

2017-12-11 Thread dam6923 .
Just to clarify, I did not help with the migration... I've been helping, piecemeal, to review comments for spelling, grammar, contractions and to remove code guards in favor of parameters. On Sat, Dec 9, 2017 at 11:22 PM, Stack wrote: > On Sat, Dec 9, 2017 at 6:03 PM, Apekshit Sharma wrote: > >>

[RESULT][VOTE] First release candidate for HBase 1.1.13 (RC0) is available

2017-12-11 Thread Nick Dimiduk
This VOTE has passed, with 3x binding +1's, a non-binding +1, and a non-binding -0. Thank you to everyone who voted on this release, and who has participated over the last 18-ish months on making branch-1.1 a successful, viable release line. I'll go about the finishing touches. Thanks, Nick On M

[jira] [Reopened] (HBASE-17425) Fix calls to deprecated APIs in TestUpdateConfiguration

2017-12-11 Thread Thiruvel Thirumoolan (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-17425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiruvel Thirumoolan reopened HBASE-17425: -- [~Jan Hentschel], Looks like HbaseTestingUtil.getAdmin() API is only in 2.x and sh

Re: Moving To SLF4J and Log4J2

2017-12-11 Thread Apekshit Sharma
Seems like good idea: - remove long dead dependency - a bit cleaner code - hadoop also moved to slf4j Quickly looking at codebase to get idea of amount of work required, here are some numbers: - LOG.debug : ~1800 - LOG.trace : ~500 - LOG.info: ~3000 Looking at this patch ( https://issues.apache.o

[jira] [Created] (HBASE-19487) Remove IterablesUtil Class

2017-12-11 Thread BELUGA BEHR (JIRA)
BELUGA BEHR created HBASE-19487: --- Summary: Remove IterablesUtil Class Key: HBASE-19487 URL: https://issues.apache.org/jira/browse/HBASE-19487 Project: HBase Issue Type: Improvement Co

Re: [VOTE] First release candidate for HBase 1.1.13 (RC0) is available

2017-12-11 Thread Mike Drob
Let's call it a -0. :) On Mon, Dec 11, 2017 at 1:14 PM, Nick Dimiduk wrote: > On Mon, Dec 11, 2017 at 8:20 AM, Mike Drob wrote: > > > Yea, this candidate is fine to promote from my perspective and given the > > other votes cast. Thanks for putting this together, Nick! > > > > Mike, > > In that

Re: [VOTE] First release candidate for HBase 1.1.13 (RC0) is available

2017-12-11 Thread Nick Dimiduk
On Mon, Dec 11, 2017 at 8:20 AM, Mike Drob wrote: > Yea, this candidate is fine to promote from my perspective and given the > other votes cast. Thanks for putting this together, Nick! > Mike, In that case, would you mind formally upgrading your vote from a -1? I'd like to remove any ambiguity

is it unnecessary for 'flushlock' in Store?

2017-12-11 Thread JH Lin
hi all, I read some code recently about the flow of flush-table which entried in HBaseAdmin#flush(tableOrRegion). i found that at least four locks in this flow(0.94): -region lock -region updatelock -hlog cacheFlushLock -store flushlock (awesome locks usages) then i have c

Re: [VOTE] First release candidate for HBase 1.1.13 (RC0) is available

2017-12-11 Thread Mike Drob
Yea, this candidate is fine to promote from my perspective and given the other votes cast. Thanks for putting this together, Nick! On Sun, Dec 10, 2017 at 7:11 PM, Nick Dimiduk wrote: > At close of the period, this VOTE has received 3x binding +1's, a > non-binding +1, and a non-binding -1, with

[jira] [Created] (HBASE-19486) Automalically flush a BufferedMutator after a timeout

2017-12-11 Thread Niels Basjes (JIRA)
Niels Basjes created HBASE-19486: Summary: Automalically flush a BufferedMutator after a timeout Key: HBASE-19486 URL: https://issues.apache.org/jira/browse/HBASE-19486 Project: HBase Issue

[jira] [Resolved] (HBASE-19294) When user trying to create table , master is getting aborted in execution phase

2017-12-11 Thread chiranjeevi (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chiranjeevi resolved HBASE-19294. - Resolution: Invalid > When user trying to create table , master is getting aborted in execution