[jira] [Updated] (HBASE-16921) TEST: update MOB unit tests to user MasterStorage/ RegionStorage APIs
[
https://issues.apache.org/jira/browse/HBASE-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-16921:
--
Release Note: test
Affects Version/s: 1.2.4
Status: Patch Available (was: Open)
test
> TEST: update MOB unit tests to user MasterStorage/ RegionStorage APIs
> -
>
> Key: HBASE-16921
> URL: https://issues.apache.org/jira/browse/HBASE-16921
> Project: HBase
> Issue Type: Sub-task
> Components: Filesystem Integration
>Affects Versions: 1.2.4
>Reporter: Umesh Agashe
>Assignee: Sean Busbey
>
> List of files:
> {code}
> hbase-server/src/test/java/org/apache/hadoop/hbase/mob/TestMobFileLink.java
> hbase-server/src/test/java/org/apache/hadoop/hbase/mob/compactions/TestPartitionedMobCompactor.java
> hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestDeleteMobTable.java
> hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHMobStore.java
> hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestMobStoreCompaction.java
> hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestMobStoreScanner.java
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (HBASE-18810) TestClientScannerRPCTimeout failing in branch-1 / branch-1.4
[
https://issues.apache.org/jira/browse/HBASE-18810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18810:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> TestClientScannerRPCTimeout failing in branch-1 / branch-1.4
>
>
> Key: HBASE-18810
> URL: https://issues.apache.org/jira/browse/HBASE-18810
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Major
> Fix For: 1.4.0
>
>
> TestClientScannerRPCTimeout is failing in branch-1 / branch-1.4, but it's a
> setup problem involving CreateTableProcedure. Fails for me the first time in
> both Linux and MacOS dev environments.
> Bisect says this is the cause, been there for a while
> {noformat}
> commit af359d03b5e2cc798cee8ba52d2a9fcbb1022104
> Author: Stephen Yuan Jiang
> Date: Tue Jul 18 06:58:29 2017 -0700
> HBASE-16488 Starting namespace and quota services in master startup
> asynchronizely (Stephen Yuan Jiang)
> {noformat}
> and sure enough, if I revert HBASE-16488 from branch-1 / branch-1.4 then the
> test passes again.
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.211 sec <<<
> FAILURE! - in org.apache.hadoop.hbase.client.TestClientScannerRPCTimeout
> testScannerNextRPCTimesout(org.apache.hadoop.hbase.client.TestClientScannerRPCTimeout)
> Time elapsed: 6.248 sec <<< ERROR!
> org.apache.hadoop.hbase.TableExistsException: testScannerNextRPCTimesout
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
> at
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
> at
> org.apache.hadoop.hbase.util.ForeignExceptionUtil.toIOException(ForeignExceptionUtil.java:45)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.convertResult(HBaseAdmin.java:4774)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.waitProcedureResult(HBaseAdmin.java:4732)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.get(HBaseAdmin.java:4665)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:679)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:1500)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:1547)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:1438)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:1414)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:1370)
> at
> org.apache.hadoop.hbase.client.TestClientScannerRPCTimeout.testScannerNextRPCTimesout(TestClientScannerRPCTimeout.java:87)
> Caused by: org.apache.hadoop.ipc.RemoteException: testScannerNextRPCTimesout
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:286)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:107)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:59)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:139)
> at
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:506)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1152)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execLoop(ProcedureExecutor.java:940)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execLoop(ProcedureExecutor.java:893)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$400(ProcedureExecutor.java:76)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.run(ProcedureExecutor.java:478)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20037) Race when calling SequenceIdAccounting.resetHighest
[ https://issues.apache.org/jira/browse/HBASE-20037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20037: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Race when calling SequenceIdAccounting.resetHighest > --- > > Key: HBASE-20037 > URL: https://issues.apache.org/jira/browse/HBASE-20037 > Project: HBase > Issue Type: Bug > Components: wal >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-20037.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18357) Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18357: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in > HBASE-14614 > > > Key: HBASE-18357 > URL: https://issues.apache.org/jira/browse/HBASE-18357 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-beta-1 >Reporter: Stephen Yuan Jiang >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-18357-v1.patch, HBASE-18357.master.001.patch > > > The Core Proc-V2 AM change in HBASE-14614 disabled two tests inTestHCM: > testMulti and testRegionCaching > This JIRA tracks the work to enable them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20020) Make sure we throw DoNotRetryIOException when ConnectionImplementation is closed
[ https://issues.apache.org/jira/browse/HBASE-20020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20020: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Make sure we throw DoNotRetryIOException when ConnectionImplementation is > closed > > > Key: HBASE-20020 > URL: https://issues.apache.org/jira/browse/HBASE-20020 > Project: HBase > Issue Type: Bug > Components: Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-20020.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18838) shaded artifacts are incorrect when built against hadoop 3
[ https://issues.apache.org/jira/browse/HBASE-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18838: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > shaded artifacts are incorrect when built against hadoop 3 > -- > > Key: HBASE-18838 > URL: https://issues.apache.org/jira/browse/HBASE-18838 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 2.0.0-alpha-3 >Reporter: Sean Busbey >Assignee: Mike Drob >Priority: Critical > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-18838-WIP.v2.patch, HBASE-18838.WIP.patch, > HBASE-18838.v3.patch, HBASE-18838.v4.patch, HBASE-18838.v5.patch > > > Building master/branch-2 against the hadoop-3 profile results in > check-invariants screaming about unrelocated dependencies. will list details > in comment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18885) HFileOutputFormat2 hardcodes default FileOutputCommitter
[ https://issues.apache.org/jira/browse/HBASE-18885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18885: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > HFileOutputFormat2 hardcodes default FileOutputCommitter > > > Key: HBASE-18885 > URL: https://issues.apache.org/jira/browse/HBASE-18885 > Project: HBase > Issue Type: Bug > Components: mapreduce >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Major > Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-4, 2.0.0 > > Attachments: HBASE-18885.branch-1.001.patch, > HBASE-18885.master.001.patch > > > Apache Kylin uses HBase's HFileOutputFormat2.java to configure the MR job. > The original reporting is in KYLIN-2788[1]. After some investigation, we > found this class always uses the default "FileOutputCommitter", see [2], > regardless of the job's configuration; so it always writing to "_temporary" > folder. Since AWS EMR configured to use DirectOutputCommitter for S3, then > this problem occurs: Hadoop expects to see the file directly under output > path, while the RecordWriter generates them in "_temporary" folder. This > caused no data be loaded to HTable. > Seems this problem exists in all versions so far. > [1] https://issues.apache.org/jira/browse/KYLIN-2788 > [2] > https://github.com/apache/hbase/blob/master/hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/HFileOutputFormat2.java#L193 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18598) AsyncNonMetaRegionLocator use FIFO algorithm to get a candidate locate request
[
https://issues.apache.org/jira/browse/HBASE-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18598:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> AsyncNonMetaRegionLocator use FIFO algorithm to get a candidate locate request
> --
>
> Key: HBASE-18598
> URL: https://issues.apache.org/jira/browse/HBASE-18598
> Project: HBase
> Issue Type: Bug
> Components: asyncclient
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Fix For: 2.0.0-alpha-2, 2.0.0
>
> Attachments: HBASE-18598-v1.patch, HBASE-18598-v2.patch,
> HBASE-18598-v2.patch
>
>
> {code}
> // TODO: use a better algorithm to send a request which is more likely to
> fetch a new
> // location.
> {code}
> After this issue, the AsyncNonMetaRegionLocator will use FIFO algorithm to
> get a candidate locate request. Meanwhile, we will clear the completed
> requests before get a candidate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19424) Metrics servlet throws NPE
[
https://issues.apache.org/jira/browse/HBASE-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19424:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Metrics servlet throws NPE
> --
>
> Key: HBASE-19424
> URL: https://issues.apache.org/jira/browse/HBASE-19424
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Andrew Purtell
>Assignee: Toshihiro Suzuki
>Priority: Minor
> Fix For: 1.3.2, 1.4.1, 1.5.0, 1.2.7, 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19424.branch-1.patch
>
>
> In branch-1 at least we put up a servlet on "/metrics" that is Hadoop's
> MetricsServlet. However HBase users are expected to pick up metrics via
> "/jmx". We don't mention "/metrics" or link to it on the UI. If you attempt
> to access "/metrics" with head of branch-1 it errors out due to a NPE
> {noformat}
> 2017-12-04 16:06:37,403 ERROR [1874557409@qtp-1910896157-3] mortbay.log:
> /metrics
> java.lang.NullPointerException
> at
> org.apache.hadoop.http.HttpServer2.isInstrumentationAccessAllowed(HttpServer2.java:1049)
> at
> org.apache.hadoop.metrics.MetricsServlet.doGet(MetricsServlet.java:109)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19015) hbase-shaded-check-invariants fails against hadoop3-beta1
[
https://issues.apache.org/jira/browse/HBASE-19015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19015:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> hbase-shaded-check-invariants fails against hadoop3-beta1
> -
>
> Key: HBASE-19015
> URL: https://issues.apache.org/jira/browse/HBASE-19015
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
> Attachments: shaded-check-invariants.out
>
>
> When using the following command trying to build tar ball against hadoop3
> beta1:
> {code}
> mvn install -DskipTests -Phadoop-3.0 -Dhadoop-three.version=3.0.0-beta1
> -Dhadoop-two.version=3.0.0-beta1 -Djetty.version=9.3.19.v20170502
> assembly:single -Prelease
> {code}
> I got the following:
> {code}
> [ERROR] Found artifact with unexpected contents:
> '/Users/tyu/.m2/repository/org/apache/hbase/hbase-shaded-client/3.0.0-SNAPSHOT/hbase-shaded-client-3.0.0-SNAPSHOT.jar'
> Please check the following and either correct the build or update
> the allowed list with reasoning.
> com/
> com/nimbusds/
> com/nimbusds/jwt/
> com/nimbusds/jwt/SignedJWT.class
> com/nimbusds/jwt/JWTClaimsSet$Builder.class
> com/nimbusds/jwt/package-info.class
> {code}
> See full output in attachment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18184) Add hbase-hadoop2-compat jar as MapReduce job dependency
[ https://issues.apache.org/jira/browse/HBASE-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18184: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Add hbase-hadoop2-compat jar as MapReduce job dependency > > > Key: HBASE-18184 > URL: https://issues.apache.org/jira/browse/HBASE-18184 > Project: HBase > Issue Type: Bug > Components: mapreduce >Affects Versions: 1.4.0, 2.0.0 >Reporter: Alex Araujo >Assignee: Alex Araujo >Priority: Minor > Fix For: 1.4.0, 2.0.0 > > Attachments: HBASE-18184.patch > > > HBASE-17448 added a dependency on hbase-hadoop2-compat for MapReduce jobs. > Explicitly add this jar dependency in TableMapReduceUtil. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19551) hbck -boundaries doesn't work correctly
[ https://issues.apache.org/jira/browse/HBASE-19551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19551: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > hbck -boundaries doesn't work correctly > --- > > Key: HBASE-19551 > URL: https://issues.apache.org/jira/browse/HBASE-19551 > Project: HBase > Issue Type: Bug > Components: hbck >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 1.4.1 > > Attachments: HBASE-19551.branch-1.patch, HBASE-19551.patch > > > Currently, in HBaseFsck#checkRegionBoundaries(), it seems like keys from > reader.getFirstKey() and reader.getLastKey() are directly compared by > ByteArrayComparator: > https://github.com/apache/hbase/blob/9d0c7c6dfbcba0907cbbc2244eac570fcc4d58a5/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java#L864-L865 > https://github.com/apache/hbase/blob/9d0c7c6dfbcba0907cbbc2244eac570fcc4d58a5/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java#L869-L870 > This is not correct because the keys consist of a key length and key itself. > We should compare rowkeys or the only key itself (by removing a key length). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19442) Backport HBASE-19065 to branch-1 (HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish)
[ https://issues.apache.org/jira/browse/HBASE-19442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19442: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-19065 to branch-1 (HRegion#bulkLoadHFiles() should wait for > concurrent Region#flush() to finish) > --- > > Key: HBASE-19442 > URL: https://issues.apache.org/jira/browse/HBASE-19442 > Project: HBase > Issue Type: Bug >Reporter: Pankaj Kumar >Assignee: Pankaj Kumar >Priority: Major > Fix For: 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-19442-branch-1.patch > > > This JIRA is to backport HBASE-19065 to branch-1/1.4/1.3/1.2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19808) Reenable TestMultiParallel
[ https://issues.apache.org/jira/browse/HBASE-19808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19808: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Reenable TestMultiParallel > -- > > Key: HBASE-19808 > URL: https://issues.apache.org/jira/browse/HBASE-19808 > Project: HBase > Issue Type: Bug > Components: test > Environment: Reenable TestMultiParallel and half of > TestRegionServerReadRequestMetrics. They depended on Master being able to > carry the system tables exclusively. Disabling this request, they work so > just enable them again. >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: 0001-HBASE-19808-Reenable-TestMultiParallel.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20005) TestFromClientSideWithCoprocessor#testCheckAndDeleteWithCompareOp occasionally fails
[
https://issues.apache.org/jira/browse/HBASE-20005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20005:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> TestFromClientSideWithCoprocessor#testCheckAndDeleteWithCompareOp
> occasionally fails
>
>
> Key: HBASE-20005
> URL: https://issues.apache.org/jira/browse/HBASE-20005
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
> Attachments: testCheckAndDeleteWithCompareOp.out
>
>
> By adding message for the assertions, the test failed at:
> {code}
> ok = table.checkAndMutate(ROW, FAMILY).qualifier(QUALIFIER)
> .ifMatches(CompareOperator.GREATER, value4).thenDelete(delete);
> -assertTrue(ok);
> +assertTrue("gr", ok);
> {code}
> I ran the test with MemoryCompactionPolicy.NONE but it still failed at the
> same place.
> Both branch-2 and master have this intermittent test failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20447) Only fail cacheBlock if block collisions aren't related to next block metadata
[ https://issues.apache.org/jira/browse/HBASE-20447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20447: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Only fail cacheBlock if block collisions aren't related to next block metadata > -- > > Key: HBASE-20447 > URL: https://issues.apache.org/jira/browse/HBASE-20447 > Project: HBase > Issue Type: Bug > Components: BlockCache, BucketCache >Affects Versions: 1.4.3, 2.0.0 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Fix For: 3.0.0, 2.1.0, 1.5.0, 1.4.5 > > Attachments: HBASE-20447.branch-1.001.patch, > HBASE-20447.branch-1.002.patch, HBASE-20447.branch-1.003.patch, > HBASE-20447.branch-1.004.patch, HBASE-20447.branch-1.005.patch, > HBASE-20447.branch-1.006.patch, HBASE-20447.master.001.patch, > HBASE-20447.master.002.patch, HBASE-20447.master.003.patch, > HBASE-20447.master.004.patch > > > This is the issue I was originally having here: > [http://mail-archives.apache.org/mod_mbox/hbase-dev/201802.mbox/%3CCAN+qs_Pav=md_aoj4xji+kcnetubg2xou2ntxv1g6m8-5vn...@mail.gmail.com%3E] > > When we pread, we don't force the read to read all of the next block header. > However, when we get into a race condition where two opener threads try to > cache the same block and one thread read all of the next block header and the > other one didn't, it will fail the open process. This is especially important > in a splitting case where it will potentially fail the split process. > Instead, in the caches, we should only fail if the required blocks are > different. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20229) ConnectionImplementation.locateRegions() returns duplicated entries when region replication is on
[
https://issues.apache.org/jira/browse/HBASE-20229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20229:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> ConnectionImplementation.locateRegions() returns duplicated entries when
> region replication is on
> -
>
> Key: HBASE-20229
> URL: https://issues.apache.org/jira/browse/HBASE-20229
> Project: HBase
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20229.branch-1.001.patch,
> HBASE-20229.branch-1.002.patch, HBASE-20229.branch-1.002.patch,
> HBASE-20229.master.001.patch, HBASE-20229.master.002.patch,
> HBASE-20229.master.003.patch, HBASE-20229.master.004.patch
>
>
> The issue is when region replication is on,
> ConnectionImplementation.locateRegions() returns duplicated entries.
> In the test in my patch, the table should have 1 primary region + 2
> secondaries, but ConnectionImplementation.locateRegions() returns 9 regions.
> Every region repeats 3 times (3 = replicas count).
> I think this is because the following code calls locateRegion() even for
> replica regions and then the result triples.
> {code:java}
> for (RegionInfo regionInfo : regions) {
> RegionLocations list = locateRegion(tableName,
> regionInfo.getStartKey(), useCache, true);
> if (list != null) {
> for (HRegionLocation loc : list.getRegionLocations()) {
> if (loc != null) {
> locations.add(loc);
> }
> }
> }
> {code}
> The fix in my patch is to make it call locateRegion() only for a primary
> region.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19754) Backport HBASE-11409 to branch-1 and branch-1.4
[ https://issues.apache.org/jira/browse/HBASE-19754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19754: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-11409 to branch-1 and branch-1.4 > --- > > Key: HBASE-19754 > URL: https://issues.apache.org/jira/browse/HBASE-19754 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0, 1.5.0 >Reporter: churro morales >Assignee: churro morales >Priority: Minor > Attachments: HBASE-19754.branch-1.patch > > > backport HBASE-11409 to branch-1, branch-1.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19315) Incorrect snapshot version is used for 2.0.0-beta-1
[ https://issues.apache.org/jira/browse/HBASE-19315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19315: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Incorrect snapshot version is used for 2.0.0-beta-1 > > > Key: HBASE-19315 > URL: https://issues.apache.org/jira/browse/HBASE-19315 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0.0-beta-1 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Minor > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-19315.branch-2.001.patch > > > Maven complains that used snapshot version is incorrect. Dot is used instead > of hyphen. > [WARNING] Some problems were encountered while building the effective model > for org.apache.hbase:hbase-error-prone:jar:2.0.0-beta-1.SNAPSHOT > [WARNING] 'version' uses an unsupported snapshot version format, should be > '*-SNAPSHOT' instead. @ line 30, column 12 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18055) Releasing L2 cache HFileBlocks before shipped() when switching from pread to stream causes result corruption
[ https://issues.apache.org/jira/browse/HBASE-18055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18055: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Releasing L2 cache HFileBlocks before shipped() when switching from pread to > stream causes result corruption > > > Key: HBASE-18055 > URL: https://issues.apache.org/jira/browse/HBASE-18055 > Project: HBase > Issue Type: Bug > Components: regionserver, Scanners >Affects Versions: 2.0.0 >Reporter: ramkrishna.s.vasudevan >Assignee: Duo Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-18055.patch > > > In HBASE-17917 tries to switch from pread to stream read when a specific size > of bytes are read. So in order to switch over, it closes the existing > scanners and creates a new scanners with pread=false. > When we close the exisitng scanners - if the blocks are served from offheap > cache we will decrement the ref count on those blocks and if it becomes zero > we make the block ready for eviction. Then there is a chance that the result > could be corrupted if new blocks occupy the cache. So the expectation was > that till the RPC call completes the response we will hold on to the blocks > that are referred by the scan. (except the last one). So trying to switch > over to stream read will break this expectation and hence > TestBlockEvictionfromclient fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19890) Canary usage should document hbase.canary.sink.class config
[ https://issues.apache.org/jira/browse/HBASE-19890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19890: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Canary usage should document hbase.canary.sink.class config > --- > > Key: HBASE-19890 > URL: https://issues.apache.org/jira/browse/HBASE-19890 > Project: HBase > Issue Type: Bug >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: HBASE-19890.master.001.patch, > HBASE-19890.master.001.patch > > > Canary#main uses config hbase.canary.sink.class to instantiate Sink class. > The Sink instance affects creation of Monitor. > In the refguide for Canary, hbase.canary.sink.class was not mentioned. > We should document this config. > Additionally, we need to document that using the default sink is not > compatible with table parameters as input so the user must change it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20066) Region sequence id may go backward after split or merge
[ https://issues.apache.org/jira/browse/HBASE-20066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20066: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Region sequence id may go backward after split or merge > --- > > Key: HBASE-20066 > URL: https://issues.apache.org/jira/browse/HBASE-20066 > Project: HBase > Issue Type: Bug >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-20066-v1.patch, HBASE-20066-v2.patch, > HBASE-20066-v3.patch, HBASE-20066-v4.patch, HBASE-20066.patch > > > The problem is that, now we have markers which will be written to WAL but not > in store file. For a normal region close, we will write a sequence id file > under the region directory, and when opening we will use this as the open > sequence id. But for split and merge, we do not copy the sequence id file to > the newly generated regions so the sequence id may go backwards since when > closing the region we will write flush marker and close marker into WAL... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19148) Reevaluate default values of configurations
[ https://issues.apache.org/jira/browse/HBASE-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19148: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Reevaluate default values of configurations > --- > > Key: HBASE-19148 > URL: https://issues.apache.org/jira/browse/HBASE-19148 > Project: HBase > Issue Type: Bug > Components: defaults >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: > 0002-HBASE-19148-Reevaluate-default-values-of-configurati.patch, > HBASE-19148.master.001.patch, HBASE-19148.master.002.patch, > HBASE-19148.master.003.patch, HBASE-19148.master.003.patch, > HBASE-19148.master.004 (1).patch, HBASE-19148.master.004.patch, > HBASE-19148.master.005.patch, HBASE-19148.master.006.patch > > > Remove cruft and mythologies. Make descriptions more digestible. Change > defaults given experience. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19784) stop-hbase gives unfriendly message when local hbase isn't running
[
https://issues.apache.org/jira/browse/HBASE-19784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19784:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> stop-hbase gives unfriendly message when local hbase isn't running
> --
>
> Key: HBASE-19784
> URL: https://issues.apache.org/jira/browse/HBASE-19784
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Minor
> Fix For: 2.0.0-beta-2, 2.0.0
>
> Attachments: HBASE-19784.patch
>
>
> {noformat}
> $ bin/stop-hbase.sh
> stopping hbasecat: /tmp/hbase-mdrob-master.pid: No such file or directory
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19332) DumpReplicationQueues misreports total WAL size
[ https://issues.apache.org/jira/browse/HBASE-19332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19332: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > DumpReplicationQueues misreports total WAL size > --- > > Key: HBASE-19332 > URL: https://issues.apache.org/jira/browse/HBASE-19332 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 1.3.1 >Reporter: Gary Helmling >Assignee: Gary Helmling >Priority: Trivial > Fix For: 1.3.2, 2.0.0 > > Attachments: HBASE-19332.patch > > > DumpReplicationQueues uses an int to collect the total WAL size for a queue. > Predictably, this overflows much of the time. Let's use a long instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20328) Fix local backup master start command in documentation
[
https://issues.apache.org/jira/browse/HBASE-20328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20328:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix local backup master start command in documentation
> --
>
> Key: HBASE-20328
> URL: https://issues.apache.org/jira/browse/HBASE-20328
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Yuki Tawara
>Assignee: Yuki Tawara
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-20328.master.001.patch
>
>
> In "2.3. Pseudo-Distributed Local Install" section of documentation, a
> command for starting backup masters lacks "start" argument.
> {noformat}
> $ ./bin/local-master-backup.sh 2 3 5
> {noformat}
> should
> {noformat}
> $ ./bin/local-master-backup.sh start 2 3 5
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18470) Remove the redundant comma from RetriesExhaustedWithDetailsException#getDesc
[ https://issues.apache.org/jira/browse/HBASE-18470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18470: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Remove the redundant comma from RetriesExhaustedWithDetailsException#getDesc > > > Key: HBASE-18470 > URL: https://issues.apache.org/jira/browse/HBASE-18470 > Project: HBase > Issue Type: Bug > Components: Client >Reporter: Benedict Jin >Assignee: Benedict Jin >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 2.0.0 > > Attachments: HBASE-18470.master.001.patch, > HBASE-18470.master.002.patch > > Original Estimate: 72h > Remaining Estimate: 72h > > The describe from `RetriesExhaustedWithDetailsException#getDesc` is ` > org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 3 > actions: FailedServerException: 3 times, `, there is a not need ', ' in the > tail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20635) Support to convert the shaded user permission proto to client user permission object
[
https://issues.apache.org/jira/browse/HBASE-20635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20635:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Support to convert the shaded user permission proto to client user permission
> object
>
>
> Key: HBASE-20635
> URL: https://issues.apache.org/jira/browse/HBASE-20635
> Project: HBase
> Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20635.patch, HBASE-20635_v2.patch,
> PHOENIX-4528_5.x-HBase-2.0_v2.patch
>
>
> Currently we have API to build the protobuf UserPermission to client user
> permission in AccessControlUtil but we cannot do the same when we use shaded
> protobufs.
> {noformat}
> /**
>* Converts a user permission proto to a client user permission object.
>*
>* @param proto the protobuf UserPermission
>* @return the converted UserPermission
>*/
> public static UserPermission
> toUserPermission(AccessControlProtos.UserPermission proto) {
> return new UserPermission(proto.getUser().toByteArray(),
> toTablePermission(proto.getPermission()));
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18617) FuzzyRowKeyFilter should not modify the filter pairs
[ https://issues.apache.org/jira/browse/HBASE-18617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18617: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > FuzzyRowKeyFilter should not modify the filter pairs > > > Key: HBASE-18617 > URL: https://issues.apache.org/jira/browse/HBASE-18617 > Project: HBase > Issue Type: Bug >Affects Versions: 1.1.2 >Reporter: vinisha >Assignee: vinisha >Priority: Minor > Fix For: 1.4.0, 2.0.0-alpha-3, 2.0.0 > > Attachments: 18617.branch-1.patch, > FuzzyRowFilter_HBASE_18617-branch-1.patch, FuzzyRowFilter_HBASE_18617_1.patch > > > Current implementation of FuzzyRowKeyFilter modifies the provided filter > pairs: > https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java#L89-L90 > Filter should not change the filter pair. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20182) Can not locate region after split and merge
[ https://issues.apache.org/jira/browse/HBASE-20182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20182: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Can not locate region after split and merge > --- > > Key: HBASE-20182 > URL: https://issues.apache.org/jira/browse/HBASE-20182 > Project: HBase > Issue Type: Bug > Components: Region Assignment >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-20182-UT.patch, HBASE-20182-addendum.patch, > HBASE-20182-v1.patch, HBASE-20182-v2.patch, HBASE-20182-v3.patch, > HBASE-20182-v3.patch, HBASE-20182-v3.patch, HBASE-20182.patch > > > When implementing serial replication feature in HBASE-20046, I found that > when splitting a region, we will not remove the parent region, instead we > will mark it offline. > And when locating a region, we will only scan one row so if we locate to the > offlined region then we are dead. > This will not happen for splitting, since one of the new daughter regions > have the same start row with the parent region, and the timestamp is greater > so when doing reverse scan we will always hit the daughter first. > But if we also consider merge then bad things happen. Consider we have two > regions A and B, we split B to C and D, and then merge A and C to E, then > ideally the regions should be E and D, but actually the regions in meta will > be E, B and D, and they all have different start rows. If you use a row > within the range of old region C, then we will always locate to B and throw > exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18093) Overloading the meaning of 'enabled' in Quota Manager to indicate either quota disabled or quota manager not ready is not good
[ https://issues.apache.org/jira/browse/HBASE-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18093: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Overloading the meaning of 'enabled' in Quota Manager to indicate either > quota disabled or quota manager not ready is not good > -- > > Key: HBASE-18093 > URL: https://issues.apache.org/jira/browse/HBASE-18093 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 1.1.10 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang >Priority: Minor > Fix For: 1.4.0, 1.2.6, 1.3.2, 1.1.11, 2.0.0 > > Attachments: HBASE-18093.v1-branch-1.patch, > HBASE-18093.v1-master.patch, HBASE-18093.v2-master.patch, > HBASE-18093.v3-master.patch > > > In MasterQuotaManager, a member 'enabled' is used to indicate either quota > feature is disabled or quota manager is not fully initialized. This would > create confusion whether caller should wait for quota manager to be > initialized or change configuration to enable quota. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20453) Shell fails to start with SyntaxError
[
https://issues.apache.org/jira/browse/HBASE-20453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20453:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Shell fails to start with SyntaxError
> -
>
> Key: HBASE-20453
> URL: https://issues.apache.org/jira/browse/HBASE-20453
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Priority: Major
>
> SyntaxError: hbase/bin/../hbase-shell/src/main/ruby/hbase/table.rb:724:
> syntax error, unexpected tDOT
> .map { |i| Bytes.toStringBinary(i.getRegionInfo().getStartKey) }
> ^
> require at org/jruby/RubyKernel.java:1062
>(root) at
> /Users/apurtell/src/hbase/bin/../hbase-shell/src/main/ruby/hbase/table.rb:25
> require at org/jruby/RubyKernel.java:1062
>(root) at
> /Users/apurtell/src/hbase/bin/../hbase-shell/src/main/ruby/hbase/hbase.rb:102
> require at org/jruby/RubyKernel.java:1062
>(root) at /Users/apurtell/src/hbase/bin/../bin/hirb.rb:107
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19304) KEEP_DELETED_CELLS should ignore case
[
https://issues.apache.org/jira/browse/HBASE-19304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19304:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> KEEP_DELETED_CELLS should ignore case
> --
>
> Key: HBASE-19304
> URL: https://issues.apache.org/jira/browse/HBASE-19304
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 2.0.0-alpha-4
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
>Priority: Blocker
> Fix For: 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19304-v1.patch
>
>
> Since HBASE-12363 we start using an enum instead of boolean for
> keep_deleted_cells. In ColumnFamilyDescriptorBuilder we are using valueOf to
> find out the value of the property. But there is a problem: all values in
> ENUM are uppercase, so if we provide the value in lowercase (and java Boolean
> returns it in lowercase in toString), the table creation may fail with an
> exception:
> {code}
> java.io.IOException: java.lang.IllegalArgumentException: No enum constant
> org.apache.hadoop.hbase.KeepDeletedCells.true
> at
> org.apache.hadoop.hbase.regionserver.HRegion.initializeStores(HRegion.java:1028)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.initializeRegionInternals(HRegion.java:891)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:859)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6966)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6923)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6894)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6850)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6801)
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:285)
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:110)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: No enum constant
> org.apache.hadoop.hbase.KeepDeletedCells.true
> at java.lang.Enum.valueOf(Enum.java:238)
> at
> org.apache.hadoop.hbase.KeepDeletedCells.valueOf(KeepDeletedCells.java:30)
> at
> org.apache.hadoop.hbase.client.ColumnFamilyDescriptorBuilder$ModifyableColumnFamilyDescriptor.lambda$getStringOrDefault$23(ColumnFamilyDescriptorBuilder.java:719)
> at
> org.apache.hadoop.hbase.client.ColumnFamilyDescriptorBuilder$ModifyableColumnFamilyDescriptor.getOrDefault(ColumnFamilyDescriptorBuilder.java:727)
> at
> org.apache.hadoop.hbase.client.ColumnFamilyDescriptorBuilder$ModifyableColumnFamilyDescriptor.getStringOrDefault(ColumnFamilyDescriptorBuilder.java:719)
> at
> org.apache.hadoop.hbase.client.ColumnFamilyDescriptorBuilder$ModifyableColumnFamilyDescriptor.getKeepDeletedCells(ColumnFamilyDescriptorBuilder.java:901)
> at
> org.apache.hadoop.hbase.regionserver.ScanInfo.(ScanInfo.java:69)
> at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:265)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:5485)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:992)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:989)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20381) precommit failing w/rat on shadedjars plugin
[ https://issues.apache.org/jira/browse/HBASE-20381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20381: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > precommit failing w/rat on shadedjars plugin > > > Key: HBASE-20381 > URL: https://issues.apache.org/jira/browse/HBASE-20381 > Project: HBase > Issue Type: Bug > Components: test >Reporter: Sean Busbey >Priority: Blocker > > see HBASE-20219 and related builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18919) branch-1.1 nightly timing out in hbase-server
[ https://issues.apache.org/jira/browse/HBASE-18919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18919: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > branch-1.1 nightly timing out in hbase-server > - > > Key: HBASE-18919 > URL: https://issues.apache.org/jira/browse/HBASE-18919 > Project: HBase > Issue Type: Bug >Affects Versions: 1.1.13 >Reporter: Sean Busbey >Priority: Critical > > branch-1.1 nightly builds have been timing out in hbase-server on jdk7: > https://builds.apache.org/job/HBase%20Nightly/job/branch-1.1/ > all recent runs look the same to me. yetus doesn't detect any hanging tests, > so I'm not sure what's hanging exactly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20854) Wrong retries number in RpcRetryingCaller's log message
[
https://issues.apache.org/jira/browse/HBASE-20854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20854:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Wrong retries number in RpcRetryingCaller's log message
> ---
>
> Key: HBASE-20854
> URL: https://issues.apache.org/jira/browse/HBASE-20854
> Project: HBase
> Issue Type: Bug
> Components: Client, logging
>Affects Versions: 2.0.0
>Reporter: Allan Yang
>Assignee: Allan Yang
>Priority: Minor
> Fix For: 3.0.0, 2.1.0, 2.0.2
>
> Attachments: HBASE-20854.branch-2.0.patch
>
>
> Just a small bug fix. In the error log message of RpcRetryingCallerImpl.
> Tries number is passed to both tries and retries. Causing a bit of confusing.
> {code:java}
> 2018-07-05 21:04:46,343 INFO [Thread-20]
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl: Call exception,
> tries=6, retries=6, started=4174 ms ago, cancelled=false,
> msg=org.apache.hadoop.hbase.exce
> ptions.RegionOpeningException: Region
> IntegrationTestBigLinkedList,\x7F\xFF\xFF\xFF\xFF\xFF\xFF\xFE,1530795739116.0cfd339596648348ac13d979150eb2bf.
> is opening on e010125049164.bja,60020,1530795698451
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20683) Incorrect return value for PreUpgradeValidator
[ https://issues.apache.org/jira/browse/HBASE-20683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20683: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Incorrect return value for PreUpgradeValidator > -- > > Key: HBASE-20683 > URL: https://issues.apache.org/jira/browse/HBASE-20683 > Project: HBase > Issue Type: Bug >Affects Versions: 3.0.0, 2.1.0, 2.0.1 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Critical > Fix For: 3.0.0, 2.1.0, 2.0.1 > > Attachments: HBASE-20683.master.001.patch, > HBASE-20683.master.002.patch > > > PreUpgradeValidator currently returns 1 when there is no incompatibilities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20385) Purge md5-making from our little make_rc.sh script
[ https://issues.apache.org/jira/browse/HBASE-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20385: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Purge md5-making from our little make_rc.sh script > -- > > Key: HBASE-20385 > URL: https://issues.apache.org/jira/browse/HBASE-20385 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-20385.master.001.patch > > > Don't generate md5s anymore. New Apache release policy via Apache > Infrastructure asks that we not provide md5 as md5 is 'broken for many > purposes; we should movea awy from it.' Remove the md5' making from our > make-rc.sh script. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18259) HBase book link to "beginner" issues includes resolved issues
[ https://issues.apache.org/jira/browse/HBASE-18259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18259: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > HBase book link to "beginner" issues includes resolved issues > - > > Key: HBASE-18259 > URL: https://issues.apache.org/jira/browse/HBASE-18259 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Mike Drob >Assignee: Peter Somogyi >Priority: Major > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-18259.master.001.patch, > HBASE-18259.master.ADDENDUM.patch > > > The link at http://hbase.apache.org/book.html#getting.involved for beginner > issues is > https://issues.apache.org/jira/issues/?jql=project%20%3D%20HBASE%20AND%20labels%20in%20(beginner) > but this includes resolved issues as well, which is not useful to folks > looking for new issues to cut their teeth on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19585) [WAL] "Unhandled: Bad type on operand stack" PBHelperClient.convert failing on HdfsProtos$ContentSummaryProto
[
https://issues.apache.org/jira/browse/HBASE-19585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19585:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> [WAL] "Unhandled: Bad type on operand stack" PBHelperClient.convert failing
> on HdfsProtos$ContentSummaryProto
> -
>
> Key: HBASE-19585
> URL: https://issues.apache.org/jira/browse/HBASE-19585
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Priority: Major
>
> Testing, RS crashes soon after startup with below cryptic mess. This is the
> branch-2 started over a 0.98 data. [~Apache9] You have a clue sir?
> {code}
> 595126 2017-12-21 13:09:38,058 INFO
> [regionserver/ve0528.halxg.cloudera.com/10.17.240.22:16020]
> wal.AbstractFSWAL: WAL configuration: blocksize=128 MB, rollsize=121.60 MB,
> prefi x=ve0528.halxg.cloudera.com%2C16020%2C1513890565537, suffix=,
> logDir=hdfs://ve0524.halxg.cloudera.com:8020/hbase/WALs/ve0528.halxg.cloudera.com,16020,1513890565537,
> archiv eDir=hdfs://ve0524.halxg.cloudera.com:8020/hbase/oldWALs
> 595127 2017-12-21 13:09:38,107 ERROR
> [regionserver/ve0528.halxg.cloudera.com/10.17.240.22:16020]
> regionserver.HRegionServer: * ABORTING region server
> ve0528.halxg.cloudera.co m,16020,1513890565537: Unhandled: Bad type on
> operand stack
> 595128 Exception Details:
> 595129 Location:
> 595130
> org/apache/hadoop/hdfs/protocolPB/PBHelperClient.convert(Lorg/apache/hadoop/hdfs/protocol/proto/HdfsProtos$ContentSummaryProto;)Lorg/apache/hadoop/fs/ContentSummary;
> @ 98: invokestatic
> 595131 Reason:
> 595132 Type 'org/apache/hadoop/fs/ContentSummary$Builder' (current frame,
> stack[1]) is not assignable to 'org/apache/hadoop/fs/QuotaUsage$Builder'
> 595133 Current Frame:
> 595134 bci: @98
> 595135 flags: { }
> 595136 locals: {
> 'org/apache/hadoop/hdfs/protocol/proto/HdfsProtos$ContentSummaryProto',
> 'org/apache/hadoop/fs/ContentSummary$Builder' }
> 595137 stack: {
> 'org/apache/hadoop/hdfs/protocol/proto/HdfsProtos$StorageTypeQuotaInfosProto',
> 'org/apache/hadoop/fs/ContentSummary$Builder' }
> 595138 Bytecode:
> 595139 0x000: 2ac7 0005 01b0 bb03 3159 b703 324c 2b2a
> 595140 0x010: b603 33b6 0334 2ab6 0335 b603 362a b603
> 595141 0x020: 37b6 0338 2ab6 0339 b603 3a2a b603 3bb6
> 595142 0x030: 033c 2ab6 033d b603 3e2a b603 3fb6 0340
> 595143 0x040: 2ab6 0341 b603 422a b603 43b6 0344 2ab6
> 595144 0x050: 0345 b603 4657 2ab6 0347 9900 0b2a b603
> 595145 0x060: 482b b803 492b b603 4ab0
> 595146 Stackmap Table:
> 595147 same_frame(@6)
> 595148 append_frame(@101,Object[#2126])
> 595149 *
> {code}
> 2.8.2 hadoop.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19364) Truncate_preserve fails with table when replica region > 1
[ https://issues.apache.org/jira/browse/HBASE-19364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19364: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Truncate_preserve fails with table when replica region > 1 > -- > > Key: HBASE-19364 > URL: https://issues.apache.org/jira/browse/HBASE-19364 > Project: HBase > Issue Type: Bug > Components: master >Reporter: Pankaj Kumar >Assignee: Pankaj Kumar >Priority: Major > Fix For: 1.5.0, 1.4.3 > > Attachments: HBASE-19364-branch-1-v2.patch, > HBASE-19364-branch-1-v3.patch, HBASE-19364-branch-1.patch, > HBASE-19364-branch-1.patch > > > Root cause is same as HBASE-17319, here we need to exclude secondary regions > while reading meta. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-17893) Allow HBase to build against Hadoop 2.8.0
[
https://issues.apache.org/jira/browse/HBASE-17893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-17893:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Allow HBase to build against Hadoop 2.8.0
> -
>
> Key: HBASE-17893
> URL: https://issues.apache.org/jira/browse/HBASE-17893
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.5
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Major
> Fix For: 1.4.0
>
> Attachments: 17883-1.2-BROKEN.txt, 17893-1.3-backport-rebased.txt,
> 17893-1.3-backport.txt, 17893.branch-1.3.patch, 17893.branch-1.patch
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project hbase-assembly: Error rendering velocity resource. Error invoking
> method 'get(java.lang.Integer)' in java.util.ArrayList at
> META-INF/LICENSE.vm[line 1671, column 8]: InvocationTargetException: Index:
> 0, Size: 0 -> [Help 1]
> {code}
> The in the generated LICENSE.
> {code}
> This product includes Nimbus JOSE+JWT licensed under the The Apache Software
> License, Version 2.0.
> ${dep.licenses[0].comments}
> Please check this License for acceptability here:
> https://www.apache.org/legal/resolved
> If it is okay, then update the list named 'non_aggregate_fine' in the
> LICENSE.vm file.
> If it isn't okay, then revert the change that added the dependency.
> More info on the dependency:
> com.nimbusds
> nimbus-jose-jwt
> 3.9
> maven central search
> g:com.nimbusds AND a:nimbus-jose-jwt AND v:3.9
> project website
> https://bitbucket.org/connect2id/nimbus-jose-jwt
> project source
> https://bitbucket.org/connect2id/nimbus-jose-jwt
> {code}
> Maybe the problem is just that it says: Apache _Software_ License
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18568) Correct metric of numRegions
[
https://issues.apache.org/jira/browse/HBASE-18568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18568:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Correct metric of numRegions
> --
>
> Key: HBASE-18568
> URL: https://issues.apache.org/jira/browse/HBASE-18568
> Project: HBase
> Issue Type: Bug
> Components: metrics
>Affects Versions: 3.0.0
>Reporter: Shibin Zhang
>Assignee: Shibin Zhang
>Priority: Critical
> Fix For: 1.4.0, 2.0.0-alpha-3, 2.0.0
>
> Attachments: HBASE-18568-V1.patch
>
>
> i found the value of metric numReigons in Regions is not correct.
> the metric can not add or remove region correctly as region close or open.
> the metric as follow:
> "name" : "Hadoop:service=HBase,name=RegionServer,sub=Regions",
> "numRegions" : 2,
> after trouble shooting ,i found the reason is in
> MetricsRegionSourceImpl#MetricsRegionSourceImpl
> {code:java}
> agg.register(this);
> ...
> hashCode = regionWrapper.getRegionHashCode();
> {code}
> when add the MetricsRegionSource to set ,but the hashCode has not yet
> initialized.
> So, the setFromMap can not put or remove the object correctly.
> it will be better like this :
> {code:java}
> hashCode = regionWrapper.getRegionHashCode();
> agg.register(this);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18137) Replication gets stuck for empty WALs
[
https://issues.apache.org/jira/browse/HBASE-18137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18137:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Replication gets stuck for empty WALs
> -
>
> Key: HBASE-18137
> URL: https://issues.apache.org/jira/browse/HBASE-18137
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Affects Versions: 1.3.1
>Reporter: Ashu Pachauri
>Assignee: Vincent Poon
>Priority: Critical
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0
>
> Attachments: HBASE-18137.branch-1.3.v1.patch,
> HBASE-18137.branch-1.3.v2.patch, HBASE-18137.branch-1.3.v3.patch,
> HBASE-18137.branch-1.v1.patch, HBASE-18137.branch-1.v2.patch,
> HBASE-18137.master.v1.patch
>
>
> Replication assumes that only the last WAL of a recovered queue can be empty.
> But, intermittent DFS issues may cause empty WALs being created (without the
> PWAL magic), and a roll of WAL to happen without a regionserver crash. This
> will cause recovered queues to have empty WALs in the middle. This cause
> replication to get stuck:
> {code}
> TRACE regionserver.ReplicationSource: Opening log
> WARN regionserver.ReplicationSource: - Got:
> java.io.EOFException
> at java.io.DataInputStream.readFully(DataInputStream.java:197)
> at java.io.DataInputStream.readFully(DataInputStream.java:169)
> at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1915)
> at
> org.apache.hadoop.io.SequenceFile$Reader.initialize(SequenceFile.java:1880)
> at
> org.apache.hadoop.io.SequenceFile$Reader.(SequenceFile.java:1829)
> at
> org.apache.hadoop.io.SequenceFile$Reader.(SequenceFile.java:1843)
> at
> org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.(SequenceFileLogReader.java:70)
> at
> org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.reset(SequenceFileLogReader.java:168)
> at
> org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.initReader(SequenceFileLogReader.java:177)
> at
> org.apache.hadoop.hbase.regionserver.wal.ReaderBase.init(ReaderBase.java:66)
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:312)
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:276)
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:264)
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:423)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationWALReaderManager.openReader(ReplicationWALReaderManager.java:70)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.openReader(ReplicationSource.java:830)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:572)
> {code}
> The WAL in question was completely empty but there were other WALs in the
> recovered queue which were newer and non-empty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20219) An error occurs when scanning with reversed=true and loadColumnFamiliesOnDemand=true
[
https://issues.apache.org/jira/browse/HBASE-20219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20219:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> An error occurs when scanning with reversed=true and
> loadColumnFamiliesOnDemand=true
>
>
> Key: HBASE-20219
> URL: https://issues.apache.org/jira/browse/HBASE-20219
> Project: HBase
> Issue Type: Bug
> Components: phoenix
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20219-UT.patch, HBASE-20219.master.001.patch,
> HBASE-20219.master.002.patch, HBASE-20219.master.003.patch,
> HBASE-20219.master.004.patch
>
>
> I'm facing the following error when scanning with reversed=true and
> loadColumnFamiliesOnDemand=true:
> {code}
> java.lang.IllegalStateException: requestSeek cannot be called on
> ReversedKeyValueHeap
> at
> org.apache.hadoop.hbase.regionserver.ReversedKeyValueHeap.requestSeek(ReversedKeyValueHeap.java:66)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.joinedHeapMayHaveData(HRegion.java:6725)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:6652)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:6364)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:3108)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:3345)
> at
> org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:41548)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
> {code}
> I will attach a UT patch to reproduce this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20364) nightly job gives old results or no results for stages that timeout on SCM
[
https://issues.apache.org/jira/browse/HBASE-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20364:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> nightly job gives old results or no results for stages that timeout on SCM
> --
>
> Key: HBASE-20364
> URL: https://issues.apache.org/jira/browse/HBASE-20364
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 1.4.4, 2.0.1
>
> Attachments: HBASE-20364.0.patch
>
>
> seen in the branch-2.0 nightly report for HBASE-18828:
>
> {quote}
> Results for branch branch-2.0
> [build #143 on
> builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143/]:
> (x) *\{color:red}-1 overall\{color}*
>
> details (if available):
> (/) \{color:green}+1 general checks\{color}
> -- For more information [see general
> report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/140//General_Nightly_Build_Report/]
>
> (/) \{color:green}+1 jdk8 hadoop2 checks\{color}
> -- For more information [see jdk8 (hadoop2)
> report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop2)/]
> (/) \{color:green}+1 jdk8 hadoop3 checks\{color}
> -- For more information [see jdk8 (hadoop3)
> report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop3)/]
>
> {quote}
>
> -1 for the overall build was correct. build #143 failed both the general
> check and the source tarball check.
>
> but in the posted comment, we get a false "passing" that links to the general
> result from build #140. and we get no result for the source tarball at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-17975) TokenUtil.obtainToken squashes remote exceptions
[
https://issues.apache.org/jira/browse/HBASE-17975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-17975:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> TokenUtil.obtainToken squashes remote exceptions
>
>
> Key: HBASE-17975
> URL: https://issues.apache.org/jira/browse/HBASE-17975
> Project: HBase
> Issue Type: Bug
> Components: mapreduce, security
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17975.0.patch
>
>
> In the changes to protobuf handling in HBASE-15638, our TokenUtil class went
> from handling remote exception via a method that would throw IOException to
> one that simply returned it. In doing so, we ended up ignoring the results.
> This causes the obtainToken method to start returning null where it would
> have previously thrown an IOException. It also causes obtainTokenForJob to
> still fail with an IOException, but instead of being the underlying remote
> problem now it's a generic "I didn't get a user token for some reason."
> found via testing Pig with errors.
> {code}
> Caused by: java.io.IOException: No token returned for user
> testu...@example.com
> at
> org.apache.hadoop.hbase.security.token.TokenUtil.obtainTokenForJob(TokenUtil.java:175)
> at
> org.apache.pig.backend.hadoop.hbase.HBaseStorage.addHBaseDelegationToken(HBaseStorage.java:887)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19643) Need to update cache location when get error in AsyncBatchRpcRetryingCaller
[ https://issues.apache.org/jira/browse/HBASE-19643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19643: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Need to update cache location when get error in AsyncBatchRpcRetryingCaller > --- > > Key: HBASE-19643 > URL: https://issues.apache.org/jira/browse/HBASE-19643 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-19643.master.001.patch, > HBASE-19643.master.002.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18844) Release hbase-2.0.0-alpha-4; Theme "Coprocessor API Cleanup"
[ https://issues.apache.org/jira/browse/HBASE-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18844: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Release hbase-2.0.0-alpha-4; Theme "Coprocessor API Cleanup" > > > Key: HBASE-18844 > URL: https://issues.apache.org/jira/browse/HBASE-18844 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-alpha-4, 2.0.0 > > Attachments: Screen Shot 2017-11-07 at 1.59.07 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20382) If RSGroups not enabled, rsgroup.jsp prints stack trace
[
https://issues.apache.org/jira/browse/HBASE-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20382:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> If RSGroups not enabled, rsgroup.jsp prints stack trace
> ---
>
> Key: HBASE-20382
> URL: https://issues.apache.org/jira/browse/HBASE-20382
> Project: HBase
> Issue Type: Bug
> Components: rsgroup, UI
>Reporter: Mike Drob
>Assignee: Balazs Meszaros
>Priority: Major
> Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-20382.branch-2.0.001.patch
>
>
> Going to {{rsgroup.jsp?name=foo}} I get the following stack trace:
> {noformat}
> org.apache.hadoop.hbase.TableNotFoundException: hbase:rsgroup
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegionInMeta(ConnectionImplementation.java:842)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:733)
> at
> org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:719)
> at
> org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:690)
> at
> org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.getRegionLocation(ConnectionImplementation.java:571)
> at
> org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.getRegionLocation(ConnectionUtils.java:131)
> at
> org.apache.hadoop.hbase.client.HRegionLocator.getRegionLocation(HRegionLocator.java:73)
> at
> org.apache.hadoop.hbase.client.RegionServerCallable.prepare(RegionServerCallable.java:223)
> at
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:105)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:385)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:359)
> at
> org.apache.hadoop.hbase.RSGroupTableAccessor.getRSGroupInfo(RSGroupTableAccessor.java:75)
> at
> org.apache.hadoop.hbase.generated.master.rsgroup_jsp._jspService(rsgroup_jsp.java:78)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
> at
> org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at
> org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at
> org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1374)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at
> org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at
> org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
>
[jira] [Issue Comment Deleted] (HBASE-20004) Client is not able to execute REST queries in a secure cluster
[ https://issues.apache.org/jira/browse/HBASE-20004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20004: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Client is not able to execute REST queries in a secure cluster > -- > > Key: HBASE-20004 > URL: https://issues.apache.org/jira/browse/HBASE-20004 > Project: HBase > Issue Type: Bug > Components: REST, security >Affects Versions: 1.3.1 >Reporter: Ashish Singhi >Assignee: Ashish Singhi >Priority: Minor > Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.5 > > Attachments: HBASE-20004.branch-1.patch, > HBASE-20004.branch-1.v1.patch, HBASE-20004.branch-1.v1.patch, > HBASE-20004.branch-2.0.patch, HBASE-20004.patch, HBASE-20004.v1.patch, > HBASE-20004.v2.patch > > > Firefox browser is not able to negotiate REST queries with server in secure > mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20350) NullPointerException in Scanner during close()
[
https://issues.apache.org/jira/browse/HBASE-20350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20350:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> NullPointerException in Scanner during close()
> --
>
> Key: HBASE-20350
> URL: https://issues.apache.org/jira/browse/HBASE-20350
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0-beta-2
>Reporter: Umesh Agashe
>Assignee: Appy
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-20350.master.001.patch
>
>
> From logs:
> {code}
> 2018-04-03 02:06:00,630 INFO org.apache.hadoop.hbase.regionserver.HRegion:
> Replaying edits from
> hdfs://ns1/hbase/data/default/IntegrationTestBigLinkedList_20180403004104/834545a2ae1baa47082a3bc7aab2be2f/recovered.edits/1032167
> 2018-04-03 02:06:00,724 INFO
> org.apache.hadoop.hbase.regionserver.RSRpcServices: Scanner
> 2120114333978460945 lease expired on region
> IntegrationTestBigLinkedList_20180403004104,\xF1\xFE\xCB\x98e1\xF8\xD4,1522742825561.ce0d91585a2d188123173c36d0b693a5.
> 2018-04-03 02:06:00,730 ERROR
> org.apache.hadoop.hbase.regionserver.HRegionServer: * ABORTING region
> server vd0510.halxg.cloudera.com,22101,1522626204176: Uncaught exception in
> executorService thread
> regionserver/vd0510.halxg.cloudera.com/10.17.226.13:22101.leaseChecker *
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.CellComparatorImpl.compareRows(CellComparatorImpl.java:202)
> at
> org.apache.hadoop.hbase.CellComparatorImpl.compare(CellComparatorImpl.java:74)
> at
> org.apache.hadoop.hbase.CellComparatorImpl.compare(CellComparatorImpl.java:61)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap$KVScannerComparator.compare(KeyValueHeap.java:207)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap$KVScannerComparator.compare(KeyValueHeap.java:190)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap$KVScannerComparator.compare(KeyValueHeap.java:178)
> at java.util.PriorityQueue.siftDownUsingComparator(PriorityQueue.java:721)
> at java.util.PriorityQueue.siftDown(PriorityQueue.java:687)
> at java.util.PriorityQueue.poll(PriorityQueue.java:595)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.close(KeyValueHeap.java:228)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.close(StoreScanner.java:483)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.close(StoreScanner.java:464)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.close(KeyValueHeap.java:224)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.close(HRegion.java:)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices$ScannerListener.leaseExpired(RSRpcServices.java:460)
> at org.apache.hadoop.hbase.regionserver.Leases.run(Leases.java:122)
> at java.lang.Thread.run(Thread.java:748)
> 2018-04-03 02:06:00,731 ERROR
> org.apache.hadoop.hbase.regionserver.HRegionServer: RegionServer abort:
> loaded coprocessors are:
> [org.apache.hadoop.hbase.security.access.AccessController,
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,
> com.cloudera.navigator.audit.hbase.RegionAuditCoProcessor]
> 2018-04-03 02:06:00,737 INFO
> org.apache.hadoop.hbase.regionserver.HRegionServer: Dump of metrics as JSON
> on abort: {
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18125) HBase shell disregards spaces at the end of a split key in a split file
[
https://issues.apache.org/jira/browse/HBASE-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18125:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HBase shell disregards spaces at the end of a split key in a split file
> ---
>
> Key: HBASE-18125
> URL: https://issues.apache.org/jira/browse/HBASE-18125
> Project: HBase
> Issue Type: Bug
> Components: shell
>Affects Versions: 1.3.1, 2.0.0
>Reporter: Ashu Pachauri
>Assignee: Chenxi Tong
>Priority: Major
> Labels: beginner
> Fix For: 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0
>
> Attachments: HBASE-18125.patch
>
>
> When converting row keys to a printable string representation, Bytes class
> considers SPACE as a printable character, so it prints it out as it is. So,
> it's quite possible that a row key has a space at the end.
> When specifying split points in a file, the row keys are not quoted and the
> shell wrapper "admin.rb" strips any whitespace off the row keys:
> {code}
> File.foreach(splits_file) do |line|
> arg[SPLITS].push(line.strip())
> end
> {code}
> The correct approach is to use "chomp()" instead of "strip()" to just strip
> off carriage returns and newlines. We should assume that the hbase user is
> either using split points printed out by hbase itself (which will not have
> tabs) or is diligent enough to not use tabs at the end of a split point.
> What's worse is that it goes undetected and will result in undesirable split
> points.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19437) Batch operation can't handle the null result for Append/Increment
[ https://issues.apache.org/jira/browse/HBASE-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19437: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Batch operation can't handle the null result for Append/Increment > - > > Key: HBASE-19437 > URL: https://issues.apache.org/jira/browse/HBASE-19437 > Project: HBase > Issue Type: Bug > Components: Usability >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-19437.v0.patch, HBASE-19437.v0.patch, > HBASE-19437.v1.patch > > > But the Table#append and #increment can handle the null result...that is an > inconsistent behavior for user. > I have noticed two scenarios that server will return null result to user. > # postAppend/postIncrement return null > # mutation.isReturnResults() is false and > preIncrementAfterRowLock/preAppendAfterRowLock doesn't return null > We should wrap the null to empty result on server side. CP user should throw > Exception rather than return null if they intend to say something is broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18413) SHORT DESCRIPTION
[ https://issues.apache.org/jira/browse/HBASE-18413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18413: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > SHORT DESCRIPTION > - > > Key: HBASE-18413 > URL: https://issues.apache.org/jira/browse/HBASE-18413 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Silvano Tamburini >Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18959) Backport HBASE-18874 (HMaster abort message will be skipped if Throwable is passed null) to branch-1
[ https://issues.apache.org/jira/browse/HBASE-18959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18959: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-18874 (HMaster abort message will be skipped if Throwable is > passed null) to branch-1 > > > Key: HBASE-18959 > URL: https://issues.apache.org/jira/browse/HBASE-18959 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0, 1.3.2, 1.5.0, 1.2.7 >Reporter: Pankaj Kumar >Assignee: Pankaj Kumar >Priority: Minor > Fix For: 1.4.0, 1.3.2 > > Attachments: HBASE-18959-branch-1.patch > > > Backport HBASE-18874 to branch-1/1.4/1.3/1.2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18100) TestBlockEvictionFromClient#testBlockRefCountAfterSplits is flaky in master branch
[
https://issues.apache.org/jira/browse/HBASE-18100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18100:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> TestBlockEvictionFromClient#testBlockRefCountAfterSplits is flaky in master
> branch
> --
>
> Key: HBASE-18100
> URL: https://issues.apache.org/jira/browse/HBASE-18100
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
> Attachments: testBlockEvictionFromClient-05-24.out
>
>
> https://builds.apache.org/job/HBASE-Flaky-Tests/lastCompletedBuild/testReport/org.apache.hadoop.hbase.client/TestBlockEvictionFromClient/testBlockRefCountAfterSplits/
> {code}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at
> org.apache.hadoop.hbase.client.TestBlockEvictionFromClient.iterateBlockCache(TestBlockEvictionFromClient.java:1215)
> at
> org.apache.hadoop.hbase.client.TestBlockEvictionFromClient.testBlockRefCountAfterSplits(TestBlockEvictionFromClient.java:607)
> {code}
> The test failed on May 16th as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19221) NoClassDefFoundError: org/hamcrest/SelfDescribing while running IT tests in 2.0-alpha4
[
https://issues.apache.org/jira/browse/HBASE-19221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19221:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> NoClassDefFoundError: org/hamcrest/SelfDescribing while running IT tests in
> 2.0-alpha4
> --
>
> Key: HBASE-19221
> URL: https://issues.apache.org/jira/browse/HBASE-19221
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0-alpha-3
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
>Priority: Blocker
> Fix For: 2.0.0-beta-1, 2.0.0
>
>
> Copying the mail from the dev@
> {code}
> I tried running some IT test cases using the alpha-4 RC. I found this issue
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/hamcrest/SelfDescribing
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> ...
>at
> org.apache.hadoop.hbase.IntegrationTestsDriver.doWork(IntegrationTestsDriver.java:111)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.IntegrationTestsDriver.main(IntegrationTestsDriver.java:47)
> The same when run against latest master it runs without any issues
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20204) Add locking to RefreshFileConnections in BucketCache
[ https://issues.apache.org/jira/browse/HBASE-20204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20204: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Add locking to RefreshFileConnections in BucketCache > > > Key: HBASE-20204 > URL: https://issues.apache.org/jira/browse/HBASE-20204 > Project: HBase > Issue Type: Bug > Components: BucketCache >Affects Versions: 1.4.3, 2.0.0 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Fix For: 3.0.0, 2.1.0, 1.5.0, 1.4.5 > > Attachments: HBASE-20204.master.001.patch, > HBASE-20204.master.002.patch, HBASE-20204.master.003.patch, > HBASE-20204.master.004.patch > > > This is a follow-up to HBASE-20141 where [~anoop.hbase] suggested adding > locking for refreshing channels. > I have also seen this become an issue when a RS has to abort and it locks on > trying to flush out the remaining data to the cache (since cache on write was > turned on). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20825) Fix pre and post hooks of CloneSnapshot and RestoreSnapshot for Access checks
[
https://issues.apache.org/jira/browse/HBASE-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20825:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix pre and post hooks of CloneSnapshot and RestoreSnapshot for Access checks
> -
>
> Key: HBASE-20825
> URL: https://issues.apache.org/jira/browse/HBASE-20825
> Project: HBase
> Issue Type: Bug
> Components: security
>Affects Versions: 2.0.0
>Reporter: Romil Choksi
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.2, 2.2.0
>
> Attachments: HBASE-20825.patch
>
>
> [~romil.choksi] found this issue during the testing.
> Steps to repro:
> 1) create a test namespace
> 2) grant 'CA' permission on that namespace to test user
> 3) access hbase shell as that test user, and create a table in that namespace
> 4) load some data into the test table
> 5) create a snapshot as test user for that test table
> 6) disable table
> 7) as test user, try restoring the snapshot onto test table
> restore_snapshot command for the test user requiring to have global admin
> access
> {code:java}
> root@ctr-e138-1518143905142-384164-01-02:~# su - hbase
> hbase@ctr-e138-1518143905142-384164-01-02:~$ kinit -kt
> /etc/security/keytabs/hbase.headless.keytab hb...@example.com
> hbase@ctr-e138-1518143905142-384164-01-02:~$ hbase shell
> HBase Shell
> Use "help" to get list of supported commands.
> Use "exit" to quit this interactive shell.
> Version 2.0.0.3.0.0.0-1565, r34730e8c13ca0887c591aef113590f4065d28964, Thu
> Jun 28 04:17:55 UTC 2018
> Took 0.0021 seconds
>
>
>
>
> hbase(main):001:0> create_namespace 'test1'
> Took 0.8544 seconds
>
>
>
>
> hbase(main):002:0> grant 'hrt_1', 'CA', '@test1'
> Took 0.5769 seconds
>
>
>
>
> hbase(main):003:0> exit
> hbase@ctr-e138-1518143905142-384164-01-02:~$ exit
> logout
>
>
>
>
> hrt_1@ctr-e138-1518143905142-384164-01-02:~$ kinit -kt
> /home/hrt_qa/hadoopqa/keytabs/hrt_1.headless.keytab hr...@example.com
> hrt_1@ctr-e138-1518143905142-384164-01-02:~$ hbase shell
> HBase Shell
> Use "help" to get list of supported commands.
> Use "exit" to quit this interactive shell.
> Version 2.0.0.3.0.0.0-1565, r34730e8c13ca0887c591aef113590f4065d28964, Thu
> Jun 28 04:17:55 UTC 2018
> Took 0.0022 seconds
> hbase(main):002:0> create 'test1:test_table', 'cf'
> Created table test1:test_table
> Took 1.8945 seconds
>
>
>
>
> => Hbase::Table - test1:test_table
> hbase(main):005:0> put 'test1:test_table', 'r1', 'cf:c1', 'v1'
> Took 0.0634 seconds
>
>
>
>
> hbase(main):006:0> put 'test1:test_table', 'r2', 'cf:c1', 'v2'
> Took 0.0054 seconds
> hbase(main):002:0> snapshot 'test1:test_table', 'snapshot_test_table'
> Took 1.1845 seconds
> hbase(main):004:0> disable 'test1:test_table'
> Took 0.4818 seconds
> hbase(main):005:0> restore_snapshot 'snapshot_test_table'
> 2018-06-28 20:44:08,639 ERROR [main] client.HBaseAdmin: Failed to restore and
> rollback to
[jira] [Issue Comment Deleted] (HBASE-19716) Fix flaky test master.assignment.TestAssignmentManager
[ https://issues.apache.org/jira/browse/HBASE-19716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19716: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Fix flaky test master.assignment.TestAssignmentManager > -- > > Key: HBASE-19716 > URL: https://issues.apache.org/jira/browse/HBASE-19716 > Project: HBase > Issue Type: Bug > Components: amv2 >Affects Versions: 2.0.0-beta-1 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0-beta-2, 2.0.0 > > > Fix flaky test: > master.assignment.TestAssignmentManager 89.7% (70 / 78). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18438) Precommit doesn't warn about unused imports
[ https://issues.apache.org/jira/browse/HBASE-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18438: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Precommit doesn't warn about unused imports > --- > > Key: HBASE-18438 > URL: https://issues.apache.org/jira/browse/HBASE-18438 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Chia-Ping Tsai >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0 > > Attachments: HBASE-18438.patch, HBASE-18438.v2.patch, > HBASE-18438.v2.patch > > > On HBASE-18419 I accidentally included an unused import in my patch, but > precommit didn't flag it. Use this issue to diagnose and fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19708) Avoid NPE when the RPC listener's accept channel is closed
[
https://issues.apache.org/jira/browse/HBASE-19708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19708:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Avoid NPE when the RPC listener's accept channel is closed
> --
>
> Key: HBASE-19708
> URL: https://issues.apache.org/jira/browse/HBASE-19708
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.98.24
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 1.3.2, 1.4.1, 1.5.0, 1.2.7
>
> Attachments: HBASE-19708-branch-1.patch, HBASE-19708-branch-1.patch
>
>
> Rare NPE when the listener's accept channel is closed. We serialize access to
> related state to avoid a previously fixed related NPE and need to do the same
> for {{acceptChannel}}. Seen in a 0.98 deploy but I think applicable to later
> code lines. Let me check.
> Exception in thread "MetadataRpcServer.handler=191,queue=0,port=60020"
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.ipc.RpcServer$Listener.getAddress(RpcServer.java:858)
> at
> org.apache.hadoop.hbase.ipc.RpcServer.getListenerAddress(RpcServer.java:2338)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:140)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19619) Modify replication_admin.rb to use ReplicationPeerConfigBuilder
[
https://issues.apache.org/jira/browse/HBASE-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19619:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Modify replication_admin.rb to use ReplicationPeerConfigBuilder
> ---
>
> Key: HBASE-19619
> URL: https://issues.apache.org/jira/browse/HBASE-19619
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Labels: shell
> Fix For: 2.0.0-beta-1, 2.0.0
>
> Attachments: 19619.v1.txt, 19619.v10.txt, 19619.v11.txt,
> 19619.v12.txt, 19619.v13.txt, 19619.v13.txt, 19619.v2.txt, 19619.v3.txt,
> 19619.v4.txt, 19619.v5.txt, 19619.v7.txt, 19619.v8.txt
>
>
> Here is the error:
> {code}
> Error:
> test_append_peer_namespaces:_works_with_namespaces_array(Hbase::ReplicationAdminTest):
> Java::JavaLang::UnsupportedOperationException:
> java.util.Collections$UnmodifiableCollection.add(java/util/Collections.java:1055)
> java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
> org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453)
> org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314)
> RUBY.block in
> add_peer_namespaces(/home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests/hbase-shell/src/main/ruby/hbase/replication_admin.rb:226)
> org.jruby.RubyArray.each(org/jruby/RubyArray.java:1734)
> org.jruby.RubyArray$INVOKER$i$0$0$each.call(org/jruby/RubyArray$INVOKER$i$0$0$each.gen)
> RUBY.add_peer_namespaces(/home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests/hbase-shell/src/main/ruby/hbase/replication_admin.rb:225)
> RUBY.command(/home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests/hbase-shell/src/main/ruby/shell/commands/append_peer_namespaces.rb:40)
> org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:522)
> {code}
> The cause was due to adding to UnmodifiableCollection
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-17993) Delete useless info log in RpcServer.processResponse
[ https://issues.apache.org/jira/browse/HBASE-17993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-17993: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Delete useless info log in RpcServer.processResponse > > > Key: HBASE-17993 > URL: https://issues.apache.org/jira/browse/HBASE-17993 > Project: HBase > Issue Type: Bug > Components: rpc >Affects Versions: 1.4.0 >Reporter: Jingyun Tian >Assignee: Jingyun Tian >Priority: Major > Labels: trivial > Fix For: 1.4.0 > > Attachments: HBASE-17993-branch-1.patch > > > There is a log which is to track what current call is. It is used to > debugging, we'd better delete it in released version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19210) TestNamespacesInstanceResource fails
[
https://issues.apache.org/jira/browse/HBASE-19210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19210:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> TestNamespacesInstanceResource fails
>
>
> Key: HBASE-19210
> URL: https://issues.apache.org/jira/browse/HBASE-19210
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 2.0.0-beta-1, 2.0.0
>
> Attachments: 19210-addendum-3.txt, 19210-addendum-4.txt,
> 19210-addendum-5.txt, 19210.addendum, 19210.v1.txt, 19210.v1.txt,
> 19210.v2.txt, 19210.v3.txt, HBASE-19210.WIP.patch
>
>
> This is the top flaky test.
> The following can be reproduced:
> {code}
> java.net.SocketException: Connection reset
> at
> org.apache.hadoop.hbase.rest.TestNamespacesInstanceResource.testInvalidNamespacePostsAndPuts(TestNamespacesInstanceResource.java:271)
> {code}
> With commit e320df5a0c267258c03909da8d0eee4c0e287532, the test passes.
> With commit 5facaded902a13556952b1f9d26b768cb86e6599, the test fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19906) TestZooKeeper Timeout
[ https://issues.apache.org/jira/browse/HBASE-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19906: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TestZooKeeper Timeout > - > > Key: HBASE-19906 > URL: https://issues.apache.org/jira/browse/HBASE-19906 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-19906.branch-2.001.patch, > HBASE-19906.branch-2.002.patch, HBASE-19906.branch-2.003.patch, > HBASE-19906.branch-2.003.patch, HBASE-19906.branch-2.004.patch, > HBASE-19906.branch-2.005.patch, HBASE-19906.branch-2.005.patch > > > TestZooKeeper is timing out causing hbase2 failures and breaking > HBASE-Flaky-Tests-branch2.0.0. > --- > Test set: org.apache.hadoop.hbase.TestZooKeeper > --- > Tests run: 6, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 600.8 s <<< > FAILURE! - in org.apache.hadoop.hbase.TestZooKeeper > org.apache.hadoop.hbase.TestZooKeeper Time elapsed: 551.041 s <<< ERROR! > org.junit.runners.model.TestTimedOutException: test timed out after 600 > seconds > at org.apache.hadoop.hbase.TestZooKeeper.after(TestZooKeeper.java:103) > org.apache.hadoop.hbase.TestZooKeeper Time elapsed: 551.046 s <<< ERROR! > java.lang.Exception: Appears to be stuck in thread > NIOServerCxn.Factory:0.0.0.0/0.0.0.0:59935 > Not always though. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-17963) RegionServers lose file locality on unplanned restart
[ https://issues.apache.org/jira/browse/HBASE-17963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-17963: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > RegionServers lose file locality on unplanned restart > - > > Key: HBASE-17963 > URL: https://issues.apache.org/jira/browse/HBASE-17963 > Project: HBase > Issue Type: Bug >Affects Versions: 1.1.2 > Environment: Evident with HDP 2.4.3 running HBase 1.1.2 >Reporter: Bjorn Olsen >Priority: Major > > When an HBase cluster crashes, HFile locality is lost. > Crashes can happen for a variety of reasons, and in this event having a quick > time to recover (both data and database performance) is critical. > On cluster restore, region servers do not load their previous set of regions, > which means all HFiles must be moved around until locality is achieved again. > Performance is poor while file locality is not close to 100%. > A major compaction must be run to move the regions around, which further > impacts performance and will take longer the more data was in HBase at the > time of the crash. > There is a graceful_stop script which is useful for planned outages - you can > first unload the regions from the region server, restart it, and then reload > the regions to the same server. No HFiles need to be moved and file locality > is quickly restored. > However, with an unplanned outage, there is no locality kept of where the > regions were. On a crash HBase randomly assigns regions to region servers and > HFile locality is very low. We then need to move all the HFiles around until > file locality is restored. > This is fine for a small number of regions and small HFiles but becomes > problematic when you have a large number of region servers or large files. > This JIRA is a request to improve this behavior for unplanned outages by > trying to restore the regions assigned per server, after a cluster restart. > For example, HBase could keep a list of the region locality at regular > intervals, and use this as an initial guideline when regions are restarted. > Locality might still not be 100% immediately - but presumably better than 0%. > It would be necessary to first disable the load balancer (if enabled) while > this restore is happening and enable it afterward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18113) Handle old client without include_stop_row flag when startRow equals endRow
[ https://issues.apache.org/jira/browse/HBASE-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18113: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Handle old client without include_stop_row flag when startRow equals endRow > --- > > Key: HBASE-18113 > URL: https://issues.apache.org/jira/browse/HBASE-18113 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0, 2.0.0 >Reporter: Phil Yang >Assignee: Phil Yang >Priority: Major > Fix For: 1.4.0, 2.0.0 > > Attachments: HBASE-18113.v02.patch, HBASE-18113.v02.patch, > HBASE-18113.v03.patch > > > Now we have include_start_row/include_stop_row flag in new version. Before > it, startRow is include and stopRow is exclude, but when startRow=endRow > there is a special logic that we consider it as a get and we should return > the value of this row to client. > In the new client, if user set start=end we will change include_stop_row to > true for behavior compatibility. > We should also do a special logic if old client access new server for > compatibility at server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20074) [FindBugs] Same code on both branches in CompactingMemStore#initMemStoreCompactor
[ https://issues.apache.org/jira/browse/HBASE-20074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20074: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > [FindBugs] Same code on both branches in > CompactingMemStore#initMemStoreCompactor > - > > Key: HBASE-20074 > URL: https://issues.apache.org/jira/browse/HBASE-20074 > Project: HBase > Issue Type: Bug > Components: findbugs >Reporter: stack >Assignee: Gali Sheffi >Priority: Major > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-20074-V01.patch > > > [~galish] Our findbugs checking was disabled for a few weeks and we just > turned it on again. It found a good one. Mind fixing it please? Meantime I've > undone the if class to get a factor dependent on index type. Thanks. > Code Warning > DB > org.apache.hadoop.hbase.regionserver.CompactingMemStore.initInmemoryFlushSize(Configuration) > uses the same code for two branches > Bug type DB_DUPLICATE_BRANCHES (click for details) > In class org.apache.hadoop.hbase.regionserver.CompactingMemStore > In method > org.apache.hadoop.hbase.regionserver.CompactingMemStore.initInmemoryFlushSize(Configuration) > At CompactingMemStore.java:[line 140] > At CompactingMemStore.java:[line 143] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19199) RatioBasedCompactionPolicy#shouldPerformMajorCompaction() always return true when only one file needs to compact
[
https://issues.apache.org/jira/browse/HBASE-19199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19199:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> RatioBasedCompactionPolicy#shouldPerformMajorCompaction() always return true
> when only one file needs to compact
>
>
> Key: HBASE-19199
> URL: https://issues.apache.org/jira/browse/HBASE-19199
> Project: HBase
> Issue Type: Bug
>Affects Versions: 3.0.0, 1.3.1, 1.4.1, 1.5.0, 2.0.0-beta-1
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19199.patch, HBASE-19199.patch, HBASE-19199.patch
>
>
> {code:title=RatioBasedCompactionPolicy.java|borderStyle=solid}
> public boolean shouldPerformMajorCompaction(Collection
> filesToCompact)
> throws IOException {
> boolean result = false;
> long mcTime = getNextMajorCompactTime(filesToCompact);
> if (filesToCompact == null || filesToCompact.isEmpty() || mcTime == 0) {
> return result;
> }
> // TODO: Use better method for determining stamp of last major
> (HBASE-2990)
> long lowTimestamp = StoreUtils.getLowestTimestamp(filesToCompact);
> long now = EnvironmentEdgeManager.currentTime();
> if (lowTimestamp > 0L && lowTimestamp < (now - mcTime)) {
> String regionInfo;
> if (this.storeConfigInfo != null && this.storeConfigInfo instanceof
> HStore) {
> regionInfo =
> ((HStore)this.storeConfigInfo).getRegionInfo().getRegionNameAsString();
> } else {
> regionInfo = this.toString();
> }
> // Major compaction time has elapsed.
> long cfTTL = HConstants.FOREVER;
> if (this.storeConfigInfo != null) {
> cfTTL = this.storeConfigInfo.getStoreFileTtl();
> }
> if (filesToCompact.size() == 1) {
> // Single file
> HStoreFile sf = filesToCompact.iterator().next();
> OptionalLong minTimestamp = sf.getMinimumTimestamp();
> long oldest = minTimestamp.isPresent() ? now -
> minTimestamp.getAsLong() : Long.MIN_VALUE;
> if (sf.isMajorCompactionResult() && (cfTTL == Long.MAX_VALUE ||
> oldest < cfTTL)) {
> float blockLocalityIndex =
> sf.getHDFSBlockDistribution().getBlockLocalityIndex(
> RSRpcServices.getHostname(comConf.conf, false));
> if (blockLocalityIndex < comConf.getMinLocalityToForceCompact()) {
> LOG.debug("Major compaction triggered on only store " + regionInfo
> + "; to make hdfs blocks local, current blockLocalityIndex is "
> + blockLocalityIndex + " (min " +
> comConf.getMinLocalityToForceCompact() + ")");
> result = true;
> } else {
> LOG.debug("Skipping major compaction of " + regionInfo
> + " because one (major) compacted file only, oldestTime " +
> oldest
> + "ms is < TTL=" + cfTTL + " and blockLocalityIndex is " +
> blockLocalityIndex
> + " (min " + comConf.getMinLocalityToForceCompact() + ")");
> }
> } else if (cfTTL != HConstants.FOREVER && oldest > cfTTL) {
> LOG.debug("Major compaction triggered on store " + regionInfo
> + ", because keyvalues outdated; time since last major compaction
> "
> + (now - lowTimestamp) + "ms");
> result = true;
> }
> } else {
> LOG.debug("Major compaction triggered on store " + regionInfo
> + "; time since last major compaction " + (now - lowTimestamp) +
> "ms");
> }
> result = true;
> }
> return result;
> }
> {code}
> {code}
>} else {
> LOG.debug("Major compaction triggered on store " + regionInfo
> + "; time since last major compaction " + (now - lowTimestamp) +
> "ms");
> }
> result = true;
> {code}
> if (lowTimestamp > 0L && lowTimestamp < (now - mcTime)), the result always
> equal true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20571) JMXJsonServlet generates invalid JSON if it has NaN in metrics
[
https://issues.apache.org/jira/browse/HBASE-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20571:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> JMXJsonServlet generates invalid JSON if it has NaN in metrics
> --
>
> Key: HBASE-20571
> URL: https://issues.apache.org/jira/browse/HBASE-20571
> Project: HBase
> Issue Type: Bug
> Components: UI
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.3.3, 2.0.1, 1.4.5
>
> Attachments: HBASE-20571.branch-1.003.patch,
> HBASE-20571.branch-1.004.patch, HBASE-20571.branch-2.0.001.patch,
> HBASE-20571.branch-2.0.002.patch, HBASE-20571.branch-2.0.002.patch,
> HBASE-20571.branch-2.0.003.patch
>
>
> {{/jmx}} servlet responses invalid JSON, if some metrics are NaN:
> {code}
> "l1CacheHitCount" : 0,
> "l1CacheMissCount" : 0,
> "l1CacheHitRatio" : NaN,
> "l1CacheMissRatio" : NaN,
> "l2CacheHitCount" : 0,
> "l2CacheMissCount" : 0,
> "l2CacheHitRatio" : 0.0,
> "l2CacheMissRatio" : 0.0,
> {code}
> NaN is an invalid character sequence in JSON. We should not response NaN in
> metrics.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18340) TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4)
[ https://issues.apache.org/jira/browse/HBASE-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18340: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4) > -- > > Key: HBASE-18340 > URL: https://issues.apache.org/jira/browse/HBASE-18340 > Project: HBase > Issue Type: Bug >Reporter: Andrew Purtell >Priority: Blocker > Fix For: 1.4.0 > > > TestAddColumnFamilyProcedure - hanging > TestCreateNamespaceProcedure - failing > TestDeleteNamespaceProcedure - failing > TestDisableTableProcedure - hanging > TestModifyColumnFamilyProcedure - hanging > TestModifyTableProcedure - hanging > TestTruncateTableProcedure - hanging > Tests are still running so this is not a complete list of all of them, but I > think they are all going to broken. Just tried TestEnableTableProcedure and > that is hanging too. > Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.63 sec <<< > FAILURE! - in > org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure > testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure) > Time elapsed: 2.053 sec <<< FAILURE! > java.lang.AssertionError: expected a running proc > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at > org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) > at > org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) > at > org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure.testRollbackAndDoubleExecution(TestCreateNamespaceProcedure.java:219) > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 525.635 sec - > in org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure > Running org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure > Tests run: 6, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 9.331 sec <<< > FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestDeleteNamespacePr > ocedure > testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure) > Time elapsed: 3.528 sec <<< FAILURE! > java.lang.AssertionError: expected a running proc > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at > org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) > at > org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) > at > org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure.testRollbackAndDoubleExecution(TestDeleteNamespaceProcedure.java:198) > Tests seem to be hanging in tearDown > "main" #1 prio=5 os_prio=31 tid=0x7fcdbd806000 nid=0x1703 in > Object.wait() [0x70218000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:186) > - locked <0x000716820ae0> (a > java.util.concurrent.atomic.AtomicBoolean) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4443) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4435) > at > org.apache.hadoop.hbase.client.HBaseAdmin.disableTableAsyncV2(HBaseAdmin.java:1370) > at > org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:1329) > at > org.apache.hadoop.hbase.HBaseTestingUtility.deleteTable(HBaseTestingUtility.java:1966) > at > org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure.tearDown(TestDisableTableProcedure.java:79) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19640) Change in filterAllRemaining() impl for FilterListWithOR
[
https://issues.apache.org/jira/browse/HBASE-19640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19640:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Change in filterAllRemaining() impl for FilterListWithOR
>
>
> Key: HBASE-19640
> URL: https://issues.apache.org/jira/browse/HBASE-19640
> Project: HBase
> Issue Type: Bug
> Components: Filters
>Affects Versions: 2.0.0-beta-1
>Reporter: Ankit Singhal
>Assignee: Zheng Hu
>Priority: Major
>
> filterAllRemaining() in FilterListWithOR will now return false if the filter
> list is empty whereas earlier it used to return true for
> Operator.MUST_PASS_ONE.
> *In HBase-2.0*
> {code}
> @Override
> public boolean filterAllRemaining() throws IOException {
> if (isEmpty()) {
> return super.filterAllRemaining();//false
> }
> for (int i = 0, n = filters.size(); i < n; i++) {
> if (!filters.get(i).filterAllRemaining()) {
> return false;
> }
> }
> return true;
> }
> {code}
> Earlier versions(1.3.1 atleast):-
> {code}
> @Override
> public boolean filterAllRemaining() throws IOException {
> int listize = filters.size();
> for (int i = 0; i < listize; i++) {
> if (filters.get(i).filterAllRemaining()) {
> if (operator == Operator.MUST_PASS_ALL) {
> return true;
> }
> } else {
> if (operator == Operator.MUST_PASS_ONE) {
> return false;
> }
> }
> }
> return operator == Operator.MUST_PASS_ONE;
> }
> {code}
> IMO, the current implementation seems to be right, but probably this change
> requires a release note at least as some people might have implemented the
> filters considering the old semantics.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19853) duplicate slf4j declaration in mapreduce pom
[ https://issues.apache.org/jira/browse/HBASE-19853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19853: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > duplicate slf4j declaration in mapreduce pom > > > Key: HBASE-19853 > URL: https://issues.apache.org/jira/browse/HBASE-19853 > Project: HBase > Issue Type: Bug > Components: dependencies >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Minor > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-19853.master.001.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20880) Fix for warning It would fail on the following input in hbase-spark
[
https://issues.apache.org/jira/browse/HBASE-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20880:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix for warning It would fail on the following input in hbase-spark
> ---
>
> Key: HBASE-20880
> URL: https://issues.apache.org/jira/browse/HBASE-20880
> Project: HBase
> Issue Type: Bug
> Environment: {code:java}
> Maven home: /opt/apache-maven-3.5.3
> Java version: 1.8.0_172, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"{code}
> last commit: 3fc23fe930aa93e8755cf2bd478bd9907f719fd2
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-20880.v01.patch
>
>
> compiling hbase-spark module returns a warning
> {code:java}
> [WARNING]
> /.../hbase/hbase-spark/src/test/scala/org/apache/hadoop/hbase/spark/TableOutputFormatSuite.scala:117:
> warning: match may not be exhaustive.
> [WARNING] It would fail on the following input: Failure((x: Throwable forSome
> x not in Exception))
> [WARNING] Try {
> [WARNING] ^
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19729) UserScanQueryMatcher#mergeFilterResponse should return INCLUDE_AND_SEEK_NEXT_ROW when filterResponse is INCLUDE_AND_SEEK_NEXT_ROW
[ https://issues.apache.org/jira/browse/HBASE-19729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19729: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > UserScanQueryMatcher#mergeFilterResponse should return > INCLUDE_AND_SEEK_NEXT_ROW when filterResponse is INCLUDE_AND_SEEK_NEXT_ROW > - > > Key: HBASE-19729 > URL: https://issues.apache.org/jira/browse/HBASE-19729 > Project: HBase > Issue Type: Bug >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Major > Labels: scanner > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-19729.v1.patch, HBASE-19729.v2.patch, > HBASE-19729.v3.patch, HBASE-19729.v4.patch, HBASE-19729.v4.patch, > addendum.patch > > > As we've discussed in HBASE-19696 > https://issues.apache.org/jira/browse/HBASE-19696?focusedCommentId=16309644=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16309644 > when (filterResponse, matchCode) = (INCLUDE_AND_SEEK_NEXT_ROW, INCLUDE) or > (INCLUDE_AND_SEEK_NEXT_ROW, INCLUDE_AND_NEXT_COL) , we should return > INCLUDE_AND_SEEK_NEXT_ROW as the merged match code. > Will upload patches for all branches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19312) Find out why sometimes we need to spend more than one second to get the cluster id
[ https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19312: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Find out why sometimes we need to spend more than one second to get the > cluster id > -- > > Key: HBASE-19312 > URL: https://issues.apache.org/jira/browse/HBASE-19312 > Project: HBase > Issue Type: Bug > Components: asyncclient, Client, Zookeeper >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 2.0.0-beta-1, 2.0.0 > > > See the discussion in HBASE-19266. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20466) Consistently use override mechanism for exempt classes in CoprocessClassloader
[ https://issues.apache.org/jira/browse/HBASE-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20466: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Consistently use override mechanism for exempt classes in CoprocessClassloader > -- > > Key: HBASE-20466 > URL: https://issues.apache.org/jira/browse/HBASE-20466 > Project: HBase > Issue Type: Bug > Components: Coprocessors >Affects Versions: 2.0.0-beta-2, 1.4.3 >Reporter: Rich Fecher >Assignee: Rich Fecher >Priority: Major > Fix For: 2.1.0 > > Attachments: HBASE-20466_master.patch, HBASE-20466_master_v2.patch, > HBASE-20466_master_v3.patch > > > RegionCoprocessorHost.testTableCoprocessorAttrs() use the inclusion list for > CoprocessorClassLoader. This issue is related to HBASE-15686. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18269) Jython docs out of date
[
https://issues.apache.org/jira/browse/HBASE-18269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18269:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Jython docs out of date
> ---
>
> Key: HBASE-18269
> URL: https://issues.apache.org/jira/browse/HBASE-18269
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Affects Versions: 1.3.1, 1.2.6, 1.5.0, 1.4.2, 2.0.0
>Reporter: Mike Drob
>Assignee: Artem Ervits
>Priority: Major
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-18269.v01.patch, HBASE-18269.v02.patch,
> HBASE-18269.v02.patch
>
>
> The documentation describing how to launch Jython + HBase is out of date. -
> https://hbase.apache.org/book.html#jython
> First, we would set the classpath differently:
> {noformat}
> HBASE_CLASSPATH=/home/hbase/jython.jar bin/hbase org.python.util.jython
> {noformat}
> Then, the actual code example is out of date too:
> {noformat}
> >>> desc = HTableDescriptor(tablename)
> >>> desc.addFamily(HColumnDescriptor("content:"))
> Traceback (most recent call last):
> File "", line 1, in
> at
> org.apache.hadoop.hbase.HColumnDescriptor.isLegalFamilyName(HColumnDescriptor.java:566)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:470)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:425)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:390)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:338)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:327)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> org.python.core.PyReflectedConstructor.constructProxy(PyReflectedConstructor.java:211)
> {noformat}
> We should make sure that the examples we claim are runnable actually are.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20842) Infinite loop when replaying remote wals
[
https://issues.apache.org/jira/browse/HBASE-20842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20842:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Infinite loop when replaying remote wals
>
>
> Key: HBASE-20842
> URL: https://issues.apache.org/jira/browse/HBASE-20842
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Reporter: Duo Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20842.master.001.patch,
> HBASE-20842.master.002.patch, HBASE-20842.master.002.patch,
> HBASE-20842.master.002.patch
>
>
> {noformat}
> 2018-07-03 12:25:11,375 WARN [RSProcedureDispatcher-pool13-t19]
> replication.SyncReplicationReplayWALRemoteProcedure(107): Replay wals
> [remoteWALs/1-replay/asf916.gq1.ygridcore.net%2C36931%2C1530620616106-1530620683061-1.1530620683075.syncrep]
> on asf916.gq1.ygridcore.net,33811,1530620636539 failed for peer id=1
> org.apache.hadoop.hbase.regionserver.RegionServerStoppedException: Server
> asf916.gq1.ygridcore.net,33811,1530620636539 is not online
> at
> org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$DeadRSRemoteCall.call(RSProcedureDispatcher.java:285)
> at
> org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$DeadRSRemoteCall.call(RSProcedureDispatcher.java:276)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2018-07-03 12:25:11,440 DEBUG [Thread-2883]
> replication.TestSyncReplicationStandbyKillRS(111): Server
> [asf916.gq1.ygridcore.net,33811,1530620636539] marked as dead, waiting for it
> to finish dead processing
> 2018-07-03 12:25:11,441 DEBUG [Thread-2883]
> replication.TestSyncReplicationStandbyKillRS(114): Server
> [asf916.gq1.ygridcore.net,33811,1530620636539] still being processed, waiting
> 2018-07-03 12:25:11,456 WARN [RS:3;asf916:45751] wal.AbstractFSWAL(419):
> 'hbase.regionserver.maxlogs' was deprecated.
> 2018-07-03 12:25:11,457 INFO [RS:3;asf916:45751] wal.AbstractFSWAL(424): WAL
> configuration: blocksize=256 MB, rollsize=128 MB,
> prefix=asf916.gq1.ygridcore.net%2C45751%2C1530620709275, suffix=,
> logDir=hdfs://localhost:42624/user/jenkins/test-data/a86a805e-162f-5f22-7b9e-573dbf0f40fb/WALs/asf916.gq1.ygridcore.net,45751,1530620709275,
>
> archiveDir=hdfs://localhost:42624/user/jenkins/test-data/a86a805e-162f-5f22-7b9e-573dbf0f40fb/oldWALs
> 2018-07-03 12:25:11,467 DEBUG [RS-EventLoopGroup-14-4]
> asyncfs.FanOutOneBlockAsyncDFSOutputSaslHelper(737): SASL client skipping
> handshake in unsecured configuration for addr = 127.0.0.1/127.0.0.1,
> datanodeId =
> DatanodeInfoWithStorage[127.0.0.1:38997,DS-6002160d-388b-4840-8538-e4c2255108be,DISK]
> 2018-07-03 12:25:11,467 DEBUG [RS-EventLoopGroup-14-5]
> asyncfs.FanOutOneBlockAsyncDFSOutputSaslHelper(737): SASL client skipping
> handshake in unsecured configuration for addr = 127.0.0.1/127.0.0.1,
> datanodeId =
> DatanodeInfoWithStorage[127.0.0.1:45904,DS-e189e3c8-a1bd-475c-86c0-3891e541fc6e,DISK]
> 2018-07-03 12:25:11,467 DEBUG [RS-EventLoopGroup-14-3]
> asyncfs.FanOutOneBlockAsyncDFSOutputSaslHelper(737): SASL client skipping
> handshake in unsecured configuration for addr = 127.0.0.1/127.0.0.1,
> datanodeId =
> DatanodeInfoWithStorage[127.0.0.1:39589,DS-62ced3f8-35c4-4904-80cc-4d514b8f4050,DISK]
> 2018-07-03 12:25:11,495 DEBUG [RegionServerTracker-0]
> procedure2.ProcedureExecutor(887): Stored pid=30,
> state=RUNNABLE:SERVER_CRASH_START; ServerCrashProcedure
> server=asf916.gq1.ygridcore.net,33811,1530620636539, splitWal=true, meta=true
> 2018-07-03 12:25:11,495 DEBUG [RegionServerTracker-0]
> assignment.AssignmentManager(1321):
> Added=asf916.gq1.ygridcore.net,33811,1530620636539 to dead servers, submitted
> shutdown handler to be executed meta=true
> 2018-07-03 12:25:11,498 INFO [PEWorker-6]
> procedure.ServerCrashProcedure(118): Start pid=30,
> state=RUNNABLE:SERVER_CRASH_START; ServerCrashProcedure
> server=asf916.gq1.ygridcore.net,33811,1530620636539, splitWal=true, meta=true
> 2018-07-03 12:25:11,500 WARN [RegionServerTracker-0]
> replication.SyncReplicationReplayWALRemoteProcedure(107): Replay wals
> [remoteWALs/1-replay/asf916.gq1.ygridcore.net%2C36931%2C1530620616106-1530620683061-1.1530620683075.syncrep]
> on asf916.gq1.ygridcore.net,33811,1530620636539 failed for peer id=1
> org.apache.hadoop.hbase.DoNotRetryIOException: server not online
> asf916.gq1.ygridcore.net,33811,1530620636539
> at
>
[jira] [Issue Comment Deleted] (HBASE-20473) Ineffective INFO logging adjustment in HFilePerformanceEvaluation
[
https://issues.apache.org/jira/browse/HBASE-20473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20473:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Ineffective INFO logging adjustment in HFilePerformanceEvaluation
> -
>
> Key: HBASE-20473
> URL: https://issues.apache.org/jira/browse/HBASE-20473
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> // Disable verbose INFO logging from org.apache.hadoop.io.compress.CodecPool
> static {
> System.setProperty("org.apache.commons.logging.Log",
> "org.apache.commons.logging.impl.SimpleLog");
> {code}
> The above code has no effect since we're migrating away from commons-logging.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19600) ITBLL failing on branch-2
[ https://issues.apache.org/jira/browse/HBASE-19600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19600: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > ITBLL failing on branch-2 > - > > Key: HBASE-19600 > URL: https://issues.apache.org/jira/browse/HBASE-19600 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1, 2.0.0 > > > Placeholder for myself. Running ITBLL on cluster w/ no chaos fails to > complete. We are missing connections. Digging. Cluster is 7 node running 8 > tasks of 25M each. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19443) HBase Client gets stuck - Cannot get replica 0 location for...
[
https://issues.apache.org/jira/browse/HBASE-19443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19443:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HBase Client gets stuck - Cannot get replica 0 location for...
> --
>
> Key: HBASE-19443
> URL: https://issues.apache.org/jira/browse/HBASE-19443
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.4
>Reporter: Lakshmiprasad D
>Priority: Critical
>
> When the loader is loading data to HBase, without any forewarning that client
> gets stuck and prints the below message continuously:
> [ERROR] AsyncProcess[hconnection-0x71f5455a-shared--pool20-t40846] Cannot get
> replica 0 location for
> {"totalColumns":20,"families":{"v":[{"timestamp":151258499,"tag":[],"qualifier":"0","vlen":4},{"timestamp":151258499,"tag":[],"qualifier":"uid","vlen":8},{"timestamp":151258499,"tag":[],"qualifier":"1","vlen":8},{"timestamp":151258499,"tag":[],"qualifier":"2","vlen":11}]},"row":"C\\x99L[5\\x80\\x00\\x00"}
> At this time no other loaders are impacted. Restart of the loader seems to
> solve the issue until next occurence.
> Upon doing jstack at this time on the loader, it is observed that process is
> stuck on a object monitor inside 'AsyncProcess.java' class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18247) Hbck to fix the case that replica region shows as key in the meta table
[
https://issues.apache.org/jira/browse/HBASE-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18247:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Hbck to fix the case that replica region shows as key in the meta table
> ---
>
> Key: HBASE-18247
> URL: https://issues.apache.org/jira/browse/HBASE-18247
> Project: HBase
> Issue Type: Bug
> Components: hbck, Operability
>Affects Versions: 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7
>
> Attachments: HBASE-18247-branch-1.2-v001.patch
>
>
> Recently, we run into one case with read replica, the replica region shows up
> as key in meta table (it is not supposed to happen, we are still working on
> why it showed up in the meta table).
> However, hbck always reported the error about the primary region. Please see
> the error attached.
> {code}
> The entry in meta table
> test,92b0201b,1492546349354_0001.c3e6f235fe7caef75f8b0fb92a012da3.
> column=info:regioninfo, timestamp=1494958820573, value={ENCODED =>
> c3e6f235fe7caef75f8b0fb92a012da3, NAME =>
> 'test,92b0201b,1492546349354_0001.c3e6f235fe7caef75f8b0fb92a012da3.',
> STARTKEY => '92b0201b', ENDKEY => '92f1a952', REPLICA_ID => 1}
> ERROR: Region { meta =>
> test,92b0201b,1492546349354.d2c637715f31a072f174e70d407fb458., hdfs => null,
> deployed => , replicaId => 0 } found in META, but not in HDFS or deployed on
> any region server.
> {code}
> Traced the code, in the following line, it does not consider the case that
> replicaId in regionInfo could be non-default.
> https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L985
> If it is changed to get replicaId from regionInfo, then hbck should be able
> to fix this by "-fixMeta".
> {code}
> diff --git
> a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> index 9eb5111..1649e53 100644
> ---
> a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> +++
> b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> @@ -982,7 +982,7 @@ public class MetaTableAccessor {
> List locations = new ArrayList<>(1);
> NavigableMap> familyMap =
> r.getNoVersionMap();
>
> -locations.add(getRegionLocation(r, regionInfo, 0));
> +locations.add(getRegionLocation(r, regionInfo,
> regionInfo.getReplicaId()));
>
> NavigableMap infoMap = familyMap.get(getCatalogFamily());
> if (infoMap == null) return new RegionLocations(locations);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19547) HBase fails building on AArch64 due to asciidoctor-maven-plugin.
[
https://issues.apache.org/jira/browse/HBASE-19547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19547:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HBase fails building on AArch64 due to asciidoctor-maven-plugin.
>
>
> Key: HBASE-19547
> URL: https://issues.apache.org/jira/browse/HBASE-19547
> Project: HBase
> Issue Type: Bug
> Components: build, documentation, website
>Affects Versions: 3.0.0
>Reporter: Yuqi Gu
>Assignee: Yuqi Gu
>Priority: Major
> Fix For: 3.0.0, 2.0.0
>
> Attachments: HBASE-19547.patch
>
>
> HBase fails building on AArch64 due to asciidoctor-maven-plugin.
> {code:java}
> mvn clean site package install -DskipTests
> [ERROR] Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.5:
> process-asciidoc (output-pdf) on project hbase:
> Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.5:
> process-asciidoc failed: (NotImplementedError)
> fstat unimplemented unsupported or native support failed to load ->
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18904) Missing break in NEXT_ROW case of FilterList#mergeReturnCodeForOrOperator()
[
https://issues.apache.org/jira/browse/HBASE-18904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18904:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Missing break in NEXT_ROW case of FilterList#mergeReturnCodeForOrOperator()
> ---
>
> Key: HBASE-18904
> URL: https://issues.apache.org/jira/browse/HBASE-18904
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Biju Nair
>Priority: Minor
> Fix For: HBASE-18410, 2.0.0
>
> Attachments: HBASE-18904.PATCH
>
>
> Here is related code, around line 569:
> {code}
> if (isInReturnCodes(rc, ReturnCode.NEXT_ROW)) {
> return ReturnCode.NEXT_ROW;
> }
> case SEEK_NEXT_USING_HINT:
> {code}
> break was missing for the NEXT_ROW case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19178:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Trivial
> Fix For: 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch, HBASE-19178.master.003.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20561) The way we stop a ReplicationSource may cause the RS down
[
https://issues.apache.org/jira/browse/HBASE-20561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20561:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> The way we stop a ReplicationSource may cause the RS down
> -
>
> Key: HBASE-20561
> URL: https://issues.apache.org/jira/browse/HBASE-20561
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Reporter: Duo Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.2.0
>
> Attachments: HBASE-20561.master.001.patch,
> HBASE-20561.master.002.patch, HBASE-20561.master.003.patch,
> HBASE-20561.master.004.patch, HBASE-20561.master.005.patch
>
>
> See this:
> https://builds.apache.org/job/HBASE-Flaky-Tests/31125/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.multiwal.TestReplicationKillMasterRSCompressedWithMultipleAsyncWAL-output.txt
> {noformat}
> 2018-05-09 15:07:00,887 INFO [RS_REFRESH_PEER-regionserver/asf916:0-1]
> regionserver.RefreshPeerCallable(52): Received a peer change event, peerId=2,
> type=REMOVE_PEER
> 2018-05-09 15:07:00,890 INFO [RS_REFRESH_PEER-regionserver/asf916:0-1]
> regionserver.ReplicationSource(485): Closing source
> 2-asf916.gq1.ygridcore.net,36287,1525878368395 because: Replication stream
> was removed by a user
> 2018-05-09 15:07:00,892 DEBUG
> [ReplicationExecutor-0.replicationSource,2-asf916.gq1.ygridcore.net,36287,1525878368395.replicationSource.shipperasf916.gq1.ygridcore.net%2C36287%2C1525878368395.asf916.gq1.ygridcore.net%2C36287%2C1525878368395.regiongroup-0,2-asf916.gq1.ygridcore.net,36287,1525878368395]
> zookeeper.ZKWatcher(617): regionserver:34308-0x163456ff2490004,
> quorum=localhost:60149, baseZNode=/1 Received InterruptedException, will
> interrupt current thread and rethrow a SystemErrorException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1406)
> at org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:871)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.delete(RecoverableZooKeeper.java:166)
> at org.apache.hadoop.hbase.zookeeper.ZKUtil.deleteNode(ZKUtil.java:1231)
> at org.apache.hadoop.hbase.zookeeper.ZKUtil.deleteNode(ZKUtil.java:1220)
> at
> org.apache.hadoop.hbase.replication.ZKReplicationQueueStorage.removeWAL(ZKReplicationQueueStorage.java:198)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.lambda$cleanOldLogs$8(ReplicationSourceManager.java:526)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.abortWhenFail(ReplicationSourceManager.java:454)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.cleanOldLogs(ReplicationSourceManager.java:526)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.cleanOldLogs(ReplicationSourceManager.java:506)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.logPositionAndCleanOldLogs(ReplicationSourceManager.java:489)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.updateLogPosition(ReplicationSourceShipper.java:231)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.shipEdits(ReplicationSourceShipper.java:133)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.run(ReplicationSourceShipper.java:103)
> 2018-05-09 15:07:00,892 DEBUG
> [ReplicationExecutor-0.replicationSource,2-asf916.gq1.ygridcore.net,36287,1525878368395.replicationSource.shipperasf916.gq1.ygridcore.net%2C36287%2C1525878368395.asf916.gq1.ygridcore.net%2C36287%2C1525878368395.regiongroup-1,2-asf916.gq1.ygridcore.net,36287,1525878368395]
> zookeeper.ZKWatcher(617): regionserver:34308-0x163456ff2490004,
> quorum=localhost:60149, baseZNode=/1 Received InterruptedException, will
> interrupt current thread and rethrow a SystemErrorException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1406)
> at org.apache.zookeeper.ZooKeeper.multiInternal(ZooKeeper.java:990)
> at org.apache.zookeeper.ZooKeeper.multi(ZooKeeper.java:910)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.multi(RecoverableZooKeeper.java:663)
> at
> org.apache.hadoop.hbase.zookeeper.ZKUtil.multiOrSequential(ZKUtil.java:1690)
> at
>
[jira] [Issue Comment Deleted] (HBASE-19509) RSGroupAdminEndpoint#preCreateTable triggers TableNotFoundException
[
https://issues.apache.org/jira/browse/HBASE-19509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19509:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> RSGroupAdminEndpoint#preCreateTable triggers TableNotFoundException
> ---
>
> Key: HBASE-19509
> URL: https://issues.apache.org/jira/browse/HBASE-19509
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0-alpha-4
>Reporter: Ted Yu
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 1.4.1, 1.5.0, 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19509-branch-1.patch, HBASE-19509.patch
>
>
> In a cluster where RS Group endpoint is installed, I noticed the following in
> master log:
> {code}
> 2017-12-13 21:42:14,230 ERROR
> [RpcServer.default.FPBQ.Fifo.handler=29,queue=2,port=2]
> master.TableStateManager: Unable to get table ltt-diff state
> org.apache.hadoop.hbase.TableNotFoundException: ltt-diff
> at
> org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:175)
> at
> org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:132)
> at
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.isTableDisabled(AssignmentManager.java:345)
> at
> org.apache.hadoop.hbase.rsgroup.RSGroupAdminServer.moveTables(RSGroupAdminServer.java:409)
> at
> org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint.assignTableToGroup(RSGroupAdminEndpoint.java:334)
> at
> org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint.preCreateTable(RSGroupAdminEndpoint.java:346)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost$11.call(MasterCoprocessorHost.java:319)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost$11.call(MasterCoprocessorHost.java:316)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:599)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:672)
> at
> org.apache.hadoop.hbase.master.MasterCoprocessorHost.preCreateTable(MasterCoprocessorHost.java:316)
> at org.apache.hadoop.hbase.master.HMaster$3.run(HMaster.java:1738)
> at
> org.apache.hadoop.hbase.master.procedure.MasterProcedureUtil.submitProcedure(MasterProcedureUtil.java:134)
> at
> org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1734)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:559)
> {code}
> It seems RSGroupAdminEndpoint#preCreateTable should take into account that
> the table doesn't exist and avoid the extraneous TableNotFoundException .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18756) HBase Book: C/C++ Apache HBase Client, the repository of FaceBook has been removed
[ https://issues.apache.org/jira/browse/HBASE-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18756: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > HBase Book: C/C++ Apache HBase Client, the repository of FaceBook has been > removed > -- > > Key: HBASE-18756 > URL: https://issues.apache.org/jira/browse/HBASE-18756 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Yung-An He >Priority: Trivial > Labels: documentation > > I found the repository of FaceBook has been removed on Hbase Book in [C/C++ > Apache HBase Client|http://hbase.apache.org/book.html#c] section. > Maybe someone has the same situation with me. > Should either the hyperlink of repository of FaceBook in [C/C++ Apache HBase > Client|http://hbase.apache.org/book.html#c] section be removed ,or do > something to make it correct ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20633) Dropping a table containing a disable violation policy fails to remove the quota upon table delete
[
https://issues.apache.org/jira/browse/HBASE-20633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20633:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Dropping a table containing a disable violation policy fails to remove the
> quota upon table delete
> --
>
> Key: HBASE-20633
> URL: https://issues.apache.org/jira/browse/HBASE-20633
> Project: HBase
> Issue Type: Bug
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.1
>
> Attachments: HBASE-20633.master.001.patch,
> HBASE-20633.master.002.patch, HBASE-20633.master.002.patch
>
>
>
> {code:java}
> private void setQuotaAndThenDropTable(SpaceViolationPolicy policy) throws
> Exception {
> Put put = new Put(Bytes.toBytes("to_reject"));
> put.addColumn(Bytes.toBytes(SpaceQuotaHelperForTests.F1),
> Bytes.toBytes("to"),
> Bytes.toBytes("reject"));
> SpaceViolationPolicy policy = SpaceViolationPolicy.DISABLE;
> // Do puts until we violate space policy
> final TableName tn = writeUntilViolationAndVerifyViolation(policy, put);
> // Now, drop the table
> TEST_UTIL.deleteTable(tn);
> LOG.debug("Successfully deleted table ", tn);
> // Now re-create the table
> TEST_UTIL.createTable(tn, Bytes.toBytes(SpaceQuotaHelperForTests.F1));
> LOG.debug("Successfully re-created table ", tn);
> // Put some rows now: should not violate as table/quota was dropped
> verifyNoViolation(policy, tn, put);
> }
> {code}
> * When we drop a table, upon completion the quota triggers removal of
> disable policy, thus causing the system to enable the table
> {noformat}
> 2018-05-18 18:08:58,189 DEBUG [PEWorker-13]
> procedure.DeleteTableProcedure(130): delete
> 'testSetQuotaAndThenDropTableWithDisable19' completed
> 2018-05-18 18:08:58,191 INFO [PEWorker-13]
> procedure2.ProcedureExecutor(1265): Finished pid=328, state=SUCCESS;
> DeleteTableProcedure table=testSetQuotaAndThenDropTableWithDisable19 in
> 271msec
> 2018-05-18 18:08:58,321 INFO [regionserver/ba4cba1aa13d:0.Chore.1]
> client.HBaseAdmin$14(844): Started enable of
> testSetQuotaAndThenDropTableWithDisable19{noformat}
> * But, since the table has already been dropped, enable procedure would
> rollback
> {noformat}
> 2018-05-18 18:08:58,427 DEBUG
> [RpcServer.default.FPBQ.Fifo.handler=2,queue=0,port=46443]
> procedure2.ProcedureExecutor(884): Stored pid=329,
> state=RUNNABLE:ENABLE_TABLE_PREPARE; EnableTableProcedure
> table=testSetQuotaAndThenDropTableWithDisable19
> 2018-05-18 18:08:58,430 DEBUG
> [RpcServer.default.FPBQ.Fifo.handler=2,queue=0,port=46443]
> master.MasterRpcServices(1141): Checking to see if procedure is done pid=329
> 2018-05-18 18:08:58,451 INFO [PEWorker-10]
> procedure2.ProcedureExecutor(1359): Rolled back pid=329, state=ROLLEDBACK,
> exception=org.apache.hadoop.hbase.TableNotFoundException via
> master-enable-table:org.apache.hadoop.hbase.TableNotFoundException:
> testSetQuotaAndThenDropTableWithDisable19; EnableTableProcedure
> table=testSetQuotaAndThenDropTableWithDisable19 exec-time=124msec
> 2018-05-18 18:08:58,533 DEBUG
> [RpcServer.default.FPBQ.Fifo.handler=2,queue=0,port=46443]
> master.MasterRpcServices(1141): Checking to see if procedure is done pid=329
> 2018-05-18 18:08:58,535 INFO [regionserver/ba4cba1aa13d:0.Chore.1]
> client.HBaseAdmin$TableFuture(3652): Operation: ENABLE, Table Name:
> default:testSetQuotaAndThenDropTableWithDisable19 failed with
> testSetQuotaAndThenDropTableWithDisable19{noformat}
> * Since, quota manager fails to enable table (i.e disable violation policy),
> it would not remove the policy, causing problems if table re-created
> {noformat}
> 2018-05-18 18:08:58,536 ERROR [regionserver/ba4cba1aa13d:0.Chore.1]
> quotas.RegionServerSpaceQuotaManager(210): Failed to disable space violation
> policy for testSetQuotaAndThenDropTableWithDisable19. This table will remain
> in violation.
> org.apache.hadoop.hbase.TableNotFoundException:
> testSetQuotaAndThenDropTableWithDisable19
> at
> org.apache.hadoop.hbase.master.procedure.EnableTableProcedure.prepareEnable(EnableTableProcedure.java:323)
> at
> org.apache.hadoop.hbase.master.procedure.EnableTableProcedure.executeFromState(EnableTableProcedure.java:98)
> at
> org.apache.hadoop.hbase.master.procedure.EnableTableProcedure.executeFromState(EnableTableProcedure.java:49)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:850)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1472)
> at
>
[jira] [Issue Comment Deleted] (HBASE-18714) The dropBehind and readahead don't be applied when useHBaseChecksum is enabled
[
https://issues.apache.org/jira/browse/HBASE-18714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18714:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> The dropBehind and readahead don't be applied when useHBaseChecksum is enabled
> --
>
> Key: HBASE-18714
> URL: https://issues.apache.org/jira/browse/HBASE-18714
> Project: HBase
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 2.0.0-alpha-3, 2.0.0
>
> Attachments: HBASE-18714.v0.patch
>
>
> {code:title=FSDataInputStreamWrapper}
> private void setStreamOptions(FSDataInputStream in) {
> try {
> this.stream.setDropBehind(dropBehind);
> } catch (Exception e) {
> // Skipped.
> }
> if (readahead >= 0) {
> try {
> this.stream.setReadahead(readahead);
> } catch (Exception e) {
> // Skipped.
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18042) Client Compatibility breaks between versions 1.2 and 1.3
[
https://issues.apache.org/jira/browse/HBASE-18042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18042:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Client Compatibility breaks between versions 1.2 and 1.3
>
>
> Key: HBASE-18042
> URL: https://issues.apache.org/jira/browse/HBASE-18042
> Project: HBase
> Issue Type: Bug
> Components: regionserver, scan
>Affects Versions: 1.4.0, 1.3.1, 2.0.0
>Reporter: Karan Mehta
>Assignee: Duo Zhang
>Priority: Critical
> Fix For: 1.4.0, 1.3.2, 2.0.0
>
> Attachments: HBASE-18042-branch-1-v1.patch,
> HBASE-18042-branch-1-v1.patch, HBASE-18042-branch-1.3-v1.patch,
> HBASE-18042-branch-1.3.patch, HBASE-18042-branch-1.patch,
> HBASE-18042-branch-1.patch, HBASE-18042-v1.patch, HBASE-18042-v2.patch,
> HBASE-18042.patch
>
>
> OpenTSDB uses AsyncHBase as its client, rather than using the traditional
> HBase Client. From version 1.2 to 1.3, the {{ClientProtos}} have been
> changed. Newer fields are added to {{ScanResponse}} proto.
> For a typical Scan request in 1.2, would require caller to make an
> OpenScanner Request, GetNextRows Request and a CloseScanner Request, based on
> {{more_rows}} boolean field in the {{ScanResponse}} proto.
> However, from 1.3, new parameter {{more_results_in_region}} was added, which
> limits the results per region. Therefore the client has to now manage sending
> all the requests for each region. Further more, if the results are exhausted
> from a particular region, the {{ScanResponse}} will set
> {{more_results_in_region}} to false, but {{more_results}} can still be true.
> Whenever the former is set to false, the {{RegionScanner}} will also be
> closed.
> OpenTSDB makes an OpenScanner Request and receives all its results in the
> first {{ScanResponse}} itself, thus creating a condition as described in
> above paragraph. Since {{more_rows}} is true, it will proceed to send next
> request at which point the {{RSRpcServices}} will throw
> {{UnknownScannerException}}. The protobuf client compatibility is maintained
> but expected behavior is modified.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20627) Relocate RS Group pre/post hooks from RSGroupAdminServer to RSGroupAdminEndpoint
[
https://issues.apache.org/jira/browse/HBASE-20627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20627:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Relocate RS Group pre/post hooks from RSGroupAdminServer to
> RSGroupAdminEndpoint
>
>
> Key: HBASE-20627
> URL: https://issues.apache.org/jira/browse/HBASE-20627
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 2.1.0, 1.4.5
>
> Attachments: 20627.branch-1.txt, 20627.v1.txt, 20627.v2.txt,
> 20627.v3.txt
>
>
> Currently RS Group pre/post hooks are called from RSGroupAdminServer.
> e.g. RSGroupAdminServer#removeRSGroup :
> {code}
> if (master.getMasterCoprocessorHost() != null) {
> master.getMasterCoprocessorHost().preRemoveRSGroup(name);
> }
> {code}
> RSGroupAdminServer#removeRSGroup is called by RSGroupAdminEndpoint :
> {code}
> checkPermission("removeRSGroup");
> groupAdminServer.removeRSGroup(request.getRSGroupName());
> {code}
> If permission check fails, the pre hook wouldn't be called.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19671) Fix TestMultiParallel#testActiveThreadsCount
[
https://issues.apache.org/jira/browse/HBASE-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19671:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix TestMultiParallel#testActiveThreadsCount
>
>
> Key: HBASE-19671
> URL: https://issues.apache.org/jira/browse/HBASE-19671
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-19671.v0.patch
>
>
> {code}
> java.lang.AssertionError: expected:<4> but was:<5>
> at
> org.apache.hadoop.hbase.client.TestMultiParallel.testActiveThreadsCount(TestMultiParallel.java:168)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18346) TestRSKilledWhenInitializing failing on branch-1 (branch-1.4)
[ https://issues.apache.org/jira/browse/HBASE-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18346: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TestRSKilledWhenInitializing failing on branch-1 (branch-1.4) > - > > Key: HBASE-18346 > URL: https://issues.apache.org/jira/browse/HBASE-18346 > Project: HBase > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Major > Fix For: 1.4.0 > > Attachments: HBASE-18346-branch-1.patch > > > Running org.apache.hadoop.hbase.regionserver.TestRSKilledWhenInitializing > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 12.343 sec > <<< FAILURE! - in > org.apache.hadoop.hbase.regionserver.TestRSKilledWhenInitiali > zing > testRSTerminationAfterRegisteringToMasterBeforeCreatingEphemeralNode(org.apache.hadoop.hbase.regionserver.TestRSKilledWhenInitializing) > Time elapsed: 12. > 329 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.regionserver.TestRSKilledWhenInitializing.testRSTerminationAfterRegisteringToMasterBeforeCreatingEphemeralNode(TestRSKi > lledWhenInitializing.java:123) > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 192.427 sec > <<< FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRSKilledWhenInitial > izing > testRSTerminationAfterRegisteringToMasterBeforeCreatingEphemeralNode(org.apache.hadoop.hbase.regionserver.TestRSKilledWhenInitializing) > Time elapsed: 179 > .859 sec <<< ERROR! > org.junit.runners.model.TestTimedOutException: test timed out after 180 > seconds > at java.lang.Thread.sleep(Native Method) > at org.apache.hadoop.hbase.util.Threads.sleep(Threads.java:146) > at > org.apache.hadoop.hbase.regionserver.TestRSKilledWhenInitializing.testRSTerminationAfterRegisteringToMasterBeforeCreatingEphemeralNode(TestRSKi > lledWhenInitializing.java:113) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19391) Calling HRegion#initializeRegionInternals from a region replica can still re-create a region directory
[ https://issues.apache.org/jira/browse/HBASE-19391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19391: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Calling HRegion#initializeRegionInternals from a region replica can still > re-create a region directory > -- > > Key: HBASE-19391 > URL: https://issues.apache.org/jira/browse/HBASE-19391 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0.0-alpha-4, 1.4.2 >Reporter: Esteban Gutierrez >Assignee: Esteban Gutierrez >Priority: Major > Fix For: 1.5.0, 2.0.0-beta-2, 1.4.3, 2.0.0 > > Attachments: > 0001-HBASE-19391-Calling-HRegion-initializeRegionInternal.patch, > HBASE-19391.master.v0.patch > > > This is a follow up from HBASE-18024. There stills a chance that attempting > to open a region that is not the default region replica can still create a > GC'd region directory by the CatalogJanitor causing inconsistencies with hbck. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19507) Get or Scan Mob by rowkey return error value when run compact_mob or major_compact_mob after change MOB_THRESHOLD bigger
[
https://issues.apache.org/jira/browse/HBASE-19507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19507:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Get or Scan Mob by rowkey return error value when run compact_mob or
> major_compact_mob after change MOB_THRESHOLD bigger
>
>
> Key: HBASE-19507
> URL: https://issues.apache.org/jira/browse/HBASE-19507
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: WangYuan
>Assignee: huaxiang sun
>Priority: Major
>
> 1、
> create 'abc',{NAME => 'cf', MOB_THRESHOLD => '10', IS_MOB => 'true'}
> put 'abc','1','cf:a','1'
> put 'abc','2','cf:a','2'
> put 'abc','3','cf:a','3'
> put 'abc','4','cf:a','y1'
> put 'abc','5','cf:a','y2'
> put 'abc','6','cf:a','y3'
>
> hbase(main):011:0> scan 'abc'
> ROWCOLUMN+CELL
>
>
> 1 column=cf:a,
> timestamp=1513171753098, value=1
>
> 2 column=cf:a,
> timestamp=1513171753208, value=2
>
> 3 column=cf:a,
> timestamp=1513171753246, value=3
>
> 4 column=cf:a,
> timestamp=1513171753273, value=y1
>
> 5 column=cf:a,
> timestamp=1513171753301, value=y2
>
> 6 column=cf:a,
> timestamp=1513171754282, value=y3
>
> hbase(main):012:0> flush 'abc'
> hbase(main):012:0> major_compact 'abc'
> hbase(main):012:0> major_compact_mob 'abc'
> 2、
> [See Hfile]:
> hbase org.apache.hadoop.hbase.io.hfile.HFile -f
> /hbase/data/default/abc/a31b3146cba0d4569a7bf44e70e299c9/cf/22a432ba5c2c4802bedd947b99626f10
> -p
> K: 1/cf:a/1513172294864/Put/vlen=5/seqid=4 V: 1
> K: 2/cf:a/1513172294892/Put/vlen=5/seqid=5 V: 2
> K: 3/cf:a/1513172294914/Put/vlen=5/seqid=6 V: 3
> K: 4/cf:a/1513172294954/Put/vlen=76/seqid=7 V:
> \x00\x00\x00\x0Ed41d8cd98f00b204e9800998ecf8427e20171213ce022548c4c3498e864fda289b81e711
> T[0]: T[1]: abc
> K: 5/cf:a/1513172294982/Put/vlen=76/seqid=8 V:
> \x00\x00\x00\x0Ed41d8cd98f00b204e9800998ecf8427e20171213ce022548c4c3498e864fda289b81e711
> T[0]: T[1]: abc
> K: 6/cf:a/1513172296455/Put/vlen=76/seqid=9 V:
> \x00\x00\x00\x0Ed41d8cd98f00b204e9800998ecf8427e20171213ce022548c4c3498e864fda289b81e711
> T[0]: T[1]: abc
> Scanned kv count -> 6
> [See Mobfile]:
> hbase org.apache.hadoop.hbase.io.hfile.HFile -f
> /hbase/mobdir/data/default/abc/07aab825b62dd9111831839cc9039df9/cf/d41d8cd98f00b204e9800998ecf8427e20171213bd8cfaf146684d4096ebf7994f050e96
> -p
> K: 4/cf:a/1513172924196/Put/vlen=14/seqid=7 V: y1
> K: 5/cf:a/1513172924214/Put/vlen=14/seqid=8 V: y2
> K: 6/cf:a/1513172925768/Put/vlen=14/seqid=9 V: y3
> 3、
> alter 'abc',{NAME => 'cf', MOB_THRESHOLD => '10240' }
> put
>
[jira] [Issue Comment Deleted] (HBASE-20106) API Compliance checker should fall back to specifying origin as remote repo
[
https://issues.apache.org/jira/browse/HBASE-20106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20106:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> API Compliance checker should fall back to specifying origin as remote repo
> ---
>
> Key: HBASE-20106
> URL: https://issues.apache.org/jira/browse/HBASE-20106
> Project: HBase
> Issue Type: Bug
> Components: API, community
>Affects Versions: 1.4.0, 1.3.2, 1.2.7, 2.0.0
>Reporter: Sean Busbey
>Assignee: Alex Leblang
>Priority: Major
> Fix For: 1.3.2, 1.5.0, 1.2.7, 1.4.3, 2.0.0
>
> Attachments: HBASE-20106.0.patch
>
>
> Since HBASE-18020 has been in the 1.4.0 release, handling the addendum here.
> {quote}
> Andrew Purtell added a comment - 08/Aug/17 19:34
> Does there need to be a documentation update too. This didn't work for me. On
> branch-1.4
> {code}
> ./dev-support/checkcompatibility.py --annotation
> org.apache.hadoop.hbase.classification.InterfaceAudience.Public --annotation
> org.apache.hadoop.hbase.classification.InterfaceAudience.LimitedPrivate
> --include-file "hbase-*" rel/1.3.1 branch-1.4
> INFO:root:Source revision: rel/1.3.1
> INFO:root:Destination revision: branch-1.4
> INFO:root:Applying JAR filename include filter: hbase-*
> INFO:root:Filtering classes using 2 annotation(s):
> INFO:root:org.apache.hadoop.hbase.classification.InterfaceAudience.Public
> INFO:root:
> org.apache.hadoop.hbase.classification.InterfaceAudience.LimitedPrivate
> INFO:root:Downloading Java ACC...
> INFO:root:Removing scratch dir /data/src/hbase/target/compat-check
> INFO:root:Creating empty scratch dir /data/src/hbase/target/compat-check
> INFO:root:Checking out 1b8ca49af872b63c7b1fbc20a6fdbe71516dd04c in
> /data/src/hbase/target/compat-check/src
> INFO:root:Checking out e9e16b59420c5d9a47b9b014b3bb3cb3421b1de9 in
> /data/src/hbase/target/compat-check/dst
> INFO:root:Building in /data/src/hbase/target/compat-check/src
> ...
> INFO:root:Will check compatibility between original jars:
>
> /data/src/hbase/target/compat-check/src/hbase-archetypes/hbase-client-project/target/hbase-client-project-1.3.1.jar
> ...
> and new jars:
>
> /data/src/hbase/target/compat-check/dst/hbase-archetypes/hbase-shaded-client-project/target/hbase-shaded-client-project-1.4.0-SNAPSHOT.jar
> ...
> Traceback (most recent call last):
> File "./dev-support/checkcompatibility.py", line 514, in
> main()
> File "./dev-support/checkcompatibility.py", line 508, in main
> dst_jars, args.annotations, skip_annotations)
> File "./dev-support/checkcompatibility.py", line 283, in run_java_acc
> "-l", get_repo_name(),
> File "./dev-support/checkcompatibility.py", line 126, in get_repo_name
> cwd=get_repo_dir()).strip()
> File "./dev-support/checkcompatibility.py", line 71, in check_output
> raise error
> subprocess.CalledProcessError: Command '['git', 'config', '--get',
> 'remote.origin.url']' returned non-zero exit status 1
> [apurtell@ip-172-31-47-35 hbase]$ git --version
> git version 1.7.1
> {code}
> {quote}
> {quote}
> awleblang Alex Leblang added a comment - 05/Sep/17 08:47
> For some reason, perhaps due to the change from bash to python, the code
> needed to explicitly state "origin/branch_name" on clean checkouts. I went
> back to look at the bash version and we use the same command, git rev-parse,
> so I'm not sure why this only just starting failing but this fixed the issue
> in all cases where I was able to replicate the failure
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
