[jira] [Issue Comment Deleted] (HBASE-18743) HFiles in use by a table which has the same name and namespace with a default table cloned from snapshot may be deleted when that snapshot and default tabl
[
https://issues.apache.org/jira/browse/HBASE-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18743:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HFiles in use by a table which has the same name and namespace with a default
> table cloned from snapshot may be deleted when that snapshot and default
> table are deleted
>
>
> Key: HBASE-18743
> URL: https://issues.apache.org/jira/browse/HBASE-18743
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.1.12
>Reporter: wenbang
>Assignee: wenbang
>Priority: Critical
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-3, 2.0.0
>
> Attachments: HBASE-18743-branch-1.patch, HBASE_18743.patch,
> HBASE_18743_v1.patch, HBASE_18743_v2.patch
>
>
> We recently had a critical production issue in which HFiles that were still
> in use by a table were deleted.
> This appears to have been caused by conditions in which table have the same
> namespace and name with a default table cloned from snapshot.when snapshot
> and default table be deleted,HFiles that are still in use may be deleted.
> For example:
> Table with default namespace is: "t1"
> The namespace of the new table is the same as the name of the default table,
> and is generated by snapshot cloned : "t1: t1"
> When the snapshot and the default namespace table are deleted, the new table
> is also deleted in the used HFiles
> This is because the creation of the BackReferenceFile get the table Name is
> not normal, resulting in can not find the reference file, hfilecleaner to
> delete the HFiles in used, when the table has not been major compact
> {code:java}
> public static boolean create(final Configuration conf, final FileSystem fs,
> final Path dstFamilyPath, final TableName linkedTable, final String
> linkedRegion,
> final String hfileName, final boolean createBackRef) throws IOException
> {
> String familyName = dstFamilyPath.getName();
> String regionName = dstFamilyPath.getParent().getName();
> String tableName =
> FSUtils.getTableName(dstFamilyPath.getParent().getParent())
> .getNameAsString();
> {code}
> {code:java}
> public static TableName getTableName(Path tablePath) {
> return TableName.valueOf(tablePath.getParent().getName(),
> tablePath.getName());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20554) "WALs outstanding" message from CleanerChore is noisy
[
https://issues.apache.org/jira/browse/HBASE-20554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20554:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> "WALs outstanding" message from CleanerChore is noisy
> -
>
> Key: HBASE-20554
> URL: https://issues.apache.org/jira/browse/HBASE-20554
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Trivial
> Fix For: 3.0.0, 2.1.0, 1.5.0, 2.0.1, 1.4.5
>
> Attachments: HBASE-20554.patch
>
>
> WARN level "WALs outstanding" from CleanerChore should be DEBUG and are not
> always correct.
> I left a cluster configured for ITBLL (retaining all WALs for post hoc
> analysis) and in the morning found the master log full of "WALs outstanding"
> warnings from CleanerChore.
> Should this really be a warning?
> {quote}
> 2018-05-09 16:42:03,893 WARN
> [node-1.cluster,16000,1525851521469_ChoreService_2] cleaner.CleanerChore:
> WALs outstanding under hdfs://node-1.cluster/hbase/oldWALs
> {quote}
> If someone has configured really long WAL retention then having WALs in
> oldWALs will be normal.
> Also, it seems the warning is sometimes incorrect.
> {quote}
> 2018-05-09 16:42:24,751 WARN
> [node-1.cluster,16000,1525851521469_ChoreService_1] cleaner.CleanerChore:
> WALs outstanding under hdfs://node-1.cluster/hbase/archive
> {quote}
> There are no WALs under archive/.
> Even at DEBUG level, if it is not correct, then it can lead an operator to be
> concerned about nothing, so better to just remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18355) Enable export snapshot tests that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18355: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Enable export snapshot tests that were disabled by Proc-V2 AM in HBASE-14614 > > > Key: HBASE-18355 > URL: https://issues.apache.org/jira/browse/HBASE-18355 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: huaxiang sun >Priority: Major > Fix For: 2.0.0-alpha-4, 2.0.0 > > Attachments: HBASE-18355-master_v001.patch, > HBASE-18355-master_v002.patch > > > The Proc-V2 AM in HBASE-14614 disabled the following tests: > - Disabled TestExportSnapshot Hangs. > - Disabled TestSecureExportSnapshot > - Disabled TestMobSecureExportSnapshot and TestMobExportSnapshot > This JIRA tracks the work to enable them. If MOB requires more work, we > could split to 2 tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20795) Allow option in BBKVComparator.compare to do comparison without sequence id
[
https://issues.apache.org/jira/browse/HBASE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20795:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Allow option in BBKVComparator.compare to do comparison without sequence id
> ---
>
> Key: HBASE-20795
> URL: https://issues.apache.org/jira/browse/HBASE-20795
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.1
>Reporter: Ankit Singhal
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.2
>
> Attachments: HBASE-20795.patch
>
>
> CellComparatorImpl#compare(final Cell a, final Cell b, boolean
> ignoreSequenceid) needs to ignore sequence id in comparison if
> ignoreSequenceId parameter is set to true but BBKVComparator.compare used
> internally for the cell of type ByteBufferKeyValue doesn't consider this.
> {code}
> @Override
> public int compare(final Cell a, final Cell b, boolean ignoreSequenceid) {
> int diff = 0;
> // "Peel off" the most common path.
> if (a instanceof ByteBufferKeyValue && b instanceof ByteBufferKeyValue) {
> diff = BBKVComparator.compare((ByteBufferKeyValue)a,
> (ByteBufferKeyValue)b);
> if (diff != 0) {
> return diff;
> }
> } else {
> diff = compareRows(a, b);
> if (diff != 0) {
> return diff;
> }
> diff = compareWithoutRow(a, b);
> if (diff != 0) {
> return diff;
> }
> }
> // Negate following comparisons so later edits show up first mvccVersion:
> later sorts first
> return ignoreSequenceid? diff: Long.compare(b.getSequenceId(),
> a.getSequenceId());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19954) Separate TestBlockReorder into individual tests to avoid ShutdownHook suppression error against hadoop3
[
https://issues.apache.org/jira/browse/HBASE-19954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19954:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Separate TestBlockReorder into individual tests to avoid ShutdownHook
> suppression error against hadoop3
>
>
> Key: HBASE-19954
> URL: https://issues.apache.org/jira/browse/HBASE-19954
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 2.0.0-beta-2, 2.0.0
>
> Attachments: 19954.v1.txt, 19954.v2.txt, 19954.v3.txt, 19954.v4.txt
>
>
> TestBlockReorder fails against hadoop 3 due to the following error:
> {code}
> 2018-02-08 17:22:23,389 ERROR [RS:0;cn012:38253]
> helpers.MarkerIgnoringBase(159): * ABORTING region server
> cn012.l42scl.hortonworks.com,38253,1518110542271: Unhandled: Failed
> suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@6a0c707e *
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@6a0c707e
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:207)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:85)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:927)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:187)
> {code}
> This is because when MiniDFSCluster is stopped in first subtest, hadoop 3
> clears ShutdownHook.
> When the 2nd test starts, suppression of ShutdownHook fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20467) Precommit personality should only run checkstyle once if we're going to run it at the root.
[
https://issues.apache.org/jira/browse/HBASE-20467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20467:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Precommit personality should only run checkstyle once if we're going to run
> it at the root.
> ---
>
> Key: HBASE-20467
> URL: https://issues.apache.org/jira/browse/HBASE-20467
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Nihal Jain
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20467.master.001.patch
>
>
> shows up v egregiously on HBASE-20332, but I've seen in a few places where
> we'll do checkstyle at top level as well on individual modules.
> eg.:
> {code}
> +1checkstyle 0m 25s hbase-common: The patch generated 0 new + 88
> unchanged - 1 fixed = 88 total (was 89)
> +1checkstyle 0m 12s The patch hbase-hadoop2-compat passed checkstyle
> +1checkstyle 0m 30s The patch hbase-client passed checkstyle
> +1checkstyle 0m 11s The patch hbase-replication passed checkstyle
> +1checkstyle 1m 15s The patch hbase-server passed checkstyle
> +1checkstyle 0m 17s The patch hbase-mapreduce passed checkstyle
> +1checkstyle 0m 8s The patch hbase-testing-util passed checkstyle
> +1checkstyle 0m 28s The patch hbase-thrift passed checkstyle
> +1checkstyle 0m 11s The patch hbase-rsgroup passed checkstyle
> +1checkstyle 0m 10s The patch hbase-shell passed checkstyle
> +1checkstyle 0m 12s The patch hbase-endpoint passed checkstyle
> +1checkstyle 0m 14s The patch hbase-backup passed checkstyle
> +1checkstyle 0m 21s The patch hbase-it passed checkstyle
> +1checkstyle 0m 14s The patch hbase-examples passed checkstyle
> +1checkstyle 0m 16s The patch hbase-rest passed checkstyle
> +1checkstyle 0m 9s The patch hbase-external-blockcache passed
> checkstyle
> +1checkstyle 0m 10s The patch hbase-shaded passed checkstyle
> +1checkstyle 0m 8s The patch hbase-shaded-mapreduce passed
> checkstyle
> +1checkstyle 0m 8s The patch hbase-shaded-check-invariants passed
> checkstyle
> +1checkstyle 0m 9s The patch
> hbase-shaded-with-hadoop-check-invariants passed checkstyle
> +1checkstyle 2m 38s root: The patch generated 0 new + 429 unchanged
> - 1 fixed = 429 total (was 430)
> {code}
> we should use the same shortcut we do with other modules when root is present
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18645) Loads of tests timing out....
[ https://issues.apache.org/jira/browse/HBASE-18645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18645: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Loads of tests timing out > - > > Key: HBASE-18645 > URL: https://issues.apache.org/jira/browse/HBASE-18645 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Chia-Ping Tsai >Priority: Critical > Attachments: HBASE-18645.master.001.patch, > HBASE-18645.master.001.patch > > > Whats up? Why are tests mostly timing out? When did it start? I can't seem to > make it happen locally so tough doing a bisect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19065) HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
[
https://issues.apache.org/jira/browse/HBASE-19065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19065:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
>
>
> Key: HBASE-19065
> URL: https://issues.apache.org/jira/browse/HBASE-19065
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1, 2.0.0
>
> Attachments: 19065.v1.txt, 19065.v2.txt, 19065.v2.txt
>
>
> When I was debugging bulk load failure, I saw the following in region server
> log:
> {code}
> 2017-10-17 23:05:28,795 DEBUG
> [B.defaultRpcServer.handler=0,queue=0,port=16020] regionserver.HRegion: NOT
> flushing memstore for region mx_,
> f449669a8b0341e4edbd2ebdacc72094f449669a8b0341e4edbd2ebdacc7209420150711,1504909319142.52d496ba39036e0c2cc9522895ad438f.,
> flushing=true, writesEnabled=true
> 2017-10-17 23:05:28,796 ERROR
> [B.defaultRpcServer.handler=0,queue=0,port=16020]
> access.SecureBulkLoadEndpoint: Failed to complete bulk load
> java.io.IOException: Could not bulk load with an assigned sequential ID
> because the flush didn't run. Reason for not flushing: Not flushing since
> already flushing
> at
> org.apache.hadoop.hbase.regionserver.HRegion.bulkLoadHFiles(HRegion.java:5282)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:292)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:275)
> {code}
> There was concurrent flush which got misinterpreted by bulkLoadHFiles().
> HRegion#bulkLoadHFiles() should wait for the concurrent flush to complete.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19185) ClassNotFoundException: com.fasterxml.jackson.*
[ https://issues.apache.org/jira/browse/HBASE-19185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19185: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > ClassNotFoundException: com.fasterxml.jackson.* > --- > > Key: HBASE-19185 > URL: https://issues.apache.org/jira/browse/HBASE-19185 > Project: HBase > Issue Type: Bug > Components: mapreduce >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Critical > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-19185.v0.patch > > > HBASE-16338 update jackson to 2.9.1 which is different from hadoop-2.7.1. We > should bring our bedding and towels and not be trying to use jackson > dependencies from hadoop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20506) Add doc and test for unused RetryCounter, useful-looking utility
[ https://issues.apache.org/jira/browse/HBASE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20506: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Add doc and test for unused RetryCounter, useful-looking utility > > > Key: HBASE-20506 > URL: https://issues.apache.org/jira/browse/HBASE-20506 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Minor > Fix For: 3.0.0, 2.1.0 > > Attachments: 20506.txt, HBASE-20506.master.001.patch, > HBASE-20506.master.002.patch > > > I thought I could use RetryCounter, old facility added years ago, for doing > backoff calculations. In the end, it didn't work for me because it is lacking > pb serialization. While trying to use it, I added a bit of doc and a test. > Might help the next dev that trips along this way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18556) change splitable to mergeable in MergeTableRegionsProcedure
[ https://issues.apache.org/jira/browse/HBASE-18556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18556: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > change splitable to mergeable in MergeTableRegionsProcedure > --- > > Key: HBASE-18556 > URL: https://issues.apache.org/jira/browse/HBASE-18556 > Project: HBase > Issue Type: Bug >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18085) Prevent parallel purge in ObjectPool
[
https://issues.apache.org/jira/browse/HBASE-18085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18085:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Prevent parallel purge in ObjectPool
>
>
> Key: HBASE-18085
> URL: https://issues.apache.org/jira/browse/HBASE-18085
> Project: HBase
> Issue Type: Bug
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-18085.patch, HBASE-18085.patch,
> e89l05465.st3.jstack
>
>
> Parallel purge in ObjectPool is meaningless and will cause contention issue
> since {{ReferenceQueue#poll}} has synchronization (source code shown below)
> {code}
> public Reference poll() {
> if (head == null)
> return null;
> synchronized (lock) {
> return reallyPoll();
> }
> }
> {code}
> We observed threads blocking on the purge method while using offheap bucket
> cache, and we could easily reproduce this by testing the 100% cache hit case
> in bucket cache with enough reading threads.
> We propose to add a purgeLock and use tryLock to avoid parallel purge.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18142) Deletion of a cell deletes the previous versions too
[ https://issues.apache.org/jira/browse/HBASE-18142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18142: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Deletion of a cell deletes the previous versions too > > > Key: HBASE-18142 > URL: https://issues.apache.org/jira/browse/HBASE-18142 > Project: HBase > Issue Type: Bug > Components: API, shell >Affects Versions: 3.0.0, 1.3.1, 1.2.6, 2.0.0-alpha-1 >Reporter: Karthick >Assignee: ChunHao >Priority: Major > Labels: beginner > Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0 > > Attachments: HBASE-18142.branch-1.v0.patch, > HBASE-18142.branch-1.v1.patch, HBASE-18142.master.v0.patch, > HBASE-18142.master.v1.patch, HBASE-18142.master.v2.patch, > HBASE-18142.master.v3.patch, HBASE-18142.master.v4.patch, > HBASE-18142.master.v5.patch, HBASE-18142.master.v6.patch, > HBASE-18142.master.v7.patch, HBASE-18142.master.v8.patch > > > When I tried to delete a cell using it's timestamp in the Hbase Shell, the > previous versions of the same cell also got deleted. But when I tried the > same using the Java API, then the previous versions are not deleted and I can > retrive the previous values. > https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java > see this file to fix the issue. This method (public Delete addColumn(final > byte [] family, final byte [] qualifier, final long timestamp)) only deletes > the current version of the cell. The previous versions are not deleted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19730) Backport HBASE-14497 Reverse Scan threw StackOverflow caused by readPt checking
[ https://issues.apache.org/jira/browse/HBASE-19730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19730: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-14497 Reverse Scan threw StackOverflow caused by readPt > checking > --- > > Key: HBASE-19730 > URL: https://issues.apache.org/jira/browse/HBASE-19730 > Project: HBase > Issue Type: Bug >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Major > Fix For: 1.2.7 > > Attachments: 19730-branch-1.2.patch, HBASE-19730.branch-1.2.patch, > branch-1.2.patch > > > HBASE-14497 fixed StackOverflowError involving reverse scan. > This issue is to backport the fix to branch-1.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20872) Cause: java.lang.RuntimeException: Failed construction of Master: class org.apache.hadoop.hbase.master.HMasterUncompilable source code - package org.apache
[
https://issues.apache.org/jira/browse/HBASE-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20872:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Cause: java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMasterUncompilable source code - package
> org.apache.hbase.thirdparty.io.netty.channel does not exist
>
>
> Key: HBASE-20872
> URL: https://issues.apache.org/jira/browse/HBASE-20872
> Project: HBase
> Issue Type: Bug
>Reporter: Artem Ervits
>Priority: Major
>
> running
> {code:java}
> mvn clean test{code}
> on hbase-spark fails with
> {code:java}
> Cause: java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMasterUncompilable source code - package
> org.apache.hbase.thirdparty.io.netty.channel does not exist
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:136)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:212)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.(LocalHBaseCluster.java:159)
> at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:250)
> at org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:121)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1042)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:988)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:859)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:853)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:782)
> ...
> Cause: java.lang.ExceptionInInitializerError:
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.setupNetty(HRegionServer.java:688)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:547)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:486)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:131)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:212)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.(LocalHBaseCluster.java:159)
> ...
> Cause: java.lang.RuntimeException: Uncompilable source code - package
> org.apache.hbase.thirdparty.io.netty.channel does not exist
> at
> org.apache.hadoop.hbase.util.NettyEventLoopGroupConfig.(NettyEventLoopGroupConfig.java:20)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.setupNetty(HRegionServer.java:688)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:547)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:486)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:131)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:212){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18227) [AMv2] Fix test hbase.coprocessor.TestCoprocessorMetrics#testRegionObserverAfterRegionClosed
[
https://issues.apache.org/jira/browse/HBASE-18227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18227:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> [AMv2] Fix test
> hbase.coprocessor.TestCoprocessorMetrics#testRegionObserverAfterRegionClosed
>
>
> Key: HBASE-18227
> URL: https://issues.apache.org/jira/browse/HBASE-18227
> Project: HBase
> Issue Type: Bug
> Components: amv2
>Affects Versions: 2.0.0-alpha-1
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-18227.master.001.patch
>
>
> When ExecuteProceduresRemoteCall in RemoteProcedureDispatcher is enabled the
> test
> hbase.coprocessor.TestCoprocessorMetrics#testRegionObserverAfterRegionClosed
> fails as it uses not supported call admin.closeRegion() to close a region.
> Disabling table later throws exception as one of the region is not online
> (already closed).
> {code}
> org.apache.hadoop.hbase.NotServingRegionException: The region
> d8c770379823cbe6cdc517327024b128 is not online, and is not opening.
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3111)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1485)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3430)
> at
> org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28757)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:406)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:278)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:258)
> 2017-06-16 11:25:02,177 WARN [RSProcedureDispatcher-pool4-t6]
> procedure.RSProcedureDispatcher$AbstractRSRemoteCall(200): the request should
> be tried elsewhere instead; server=172.21.2.192,53652,1497637493318 try=0
> org.apache.hadoop.hbase.NotServingRegionException:
> org.apache.hadoop.hbase.NotServingRegionException: The region
> d8c770379823cbe6cdc517327024b128 is not online, and is not opening.
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3111)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1485)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3430)
> at
> org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28757)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:406)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:278)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:258)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:93)
> at
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:83)
> at
> org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:370)
> at
> org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:347)
> at
> org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.sendRequest(RSProcedureDispatcher.java:295)
> at
> org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:265)
> at
> org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:246)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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:
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
> org.apache.hadoop.hbase.NotServingRegionException: The region
>
[jira] [Issue Comment Deleted] (HBASE-20376) RowCounter and CellCounter documentations are incorrect
[ https://issues.apache.org/jira/browse/HBASE-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20376: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > RowCounter and CellCounter documentations are incorrect > --- > > Key: HBASE-20376 > URL: https://issues.apache.org/jira/browse/HBASE-20376 > Project: HBase > Issue Type: Bug > Components: documentation, mapreduce >Affects Versions: 2.0.0 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Minor > Fix For: 3.0.0, 2.0.0 > > Attachments: HBASE-20376.master.001.patch, > HBASE-20376.master.002.patch, HBASE-20376.master.003.patch > > > The documentation of RowCounter and CellCounter in refguide needs some > improvement. Help messages also need some tuning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20114) Fix IllegalFormatConversionException in rsgroup.jsp
[
https://issues.apache.org/jira/browse/HBASE-20114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20114:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix IllegalFormatConversionException in rsgroup.jsp
> ---
>
> Key: HBASE-20114
> URL: https://issues.apache.org/jira/browse/HBASE-20114
> Project: HBase
> Issue Type: Bug
> Components: UI
>Affects Versions: 3.0.0, 2.0.0-beta-2
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Labels: CE
> Fix For: 2.0.0
>
> Attachments: HBASE-20114.branch-2.001.patch
>
>
> IllegalFormatConversionException at
> {code:java}
> String.format("%.0f", sl.getRequestCountPerSecond())
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19025) Hbase MasterProcWALs getting pile up
[ https://issues.apache.org/jira/browse/HBASE-19025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19025: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Hbase MasterProcWALs getting pile up > > > Key: HBASE-19025 > URL: https://issues.apache.org/jira/browse/HBASE-19025 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.6 >Reporter: Irfan >Priority: Major > > MasterProcWALs getting pile up and getting below error in Hmaster log > 2017-10-17 03:34:42,141 INFO [ip-176-0-0-44:16000.activeMasterManager] > hdfs.DFSClient: Successfully connected to /176.0.0.29:50010 for > BP-1665161556-176.0. > 0.44-1498805562805:blk_1073773522_32746 > 2017-10-17 03:34:42,182 INFO [ip-176-0-0-44:16000.activeMasterManager] > util.FSHDFSUtils: Recover lease on dfs file > hdfs://192.168.168.1:9000/hbase2/MasterProcWALs/state-5592.log > 2017-10-17 03:34:42,182 INFO [ip-176-0-0-44:16000.activeMasterManager] > util.FSHDFSUtils: Recovered lease, attempt=0 on > file=hdfs://ec2-34-195-113-113.compu > te-1.amazonaws.com:9000/hbase2/MasterProcWALs/state-5592.log > after 0ms > 2017-10-17 03:34:42,184 WARN [ip-176-0-0-44:16000.activeMasterManager] > hdfs.BlockReaderFactory: I/O error constructing remote block reader. > java.io.IOException: Got error, status message opReadBlock > BP-1665161556-176.0.0.44-1498805562805:blk_1073773523_32747 received > exception java.io.FileNotFou > ndException: > /data/datanode/data/current/BP-1665161556-176.0.0.44-1498805562805/current/finalized/subdir0/subdir123/blk_1073773523_32747.meta > (Too many open > files), for OP_READ_BLOCK, self=/176.0.0.44:59340, remote=/176.0.0.44:50010, > for file /hbase2/MasterProcWALs/state-5592.log, for pool BP-16 > 65161556-176.0.0.44-1498805562805 block 1073773523_32747 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20280) Fix possibility of deadlocking in refreshFileConnections when prefetch is enabled
[ https://issues.apache.org/jira/browse/HBASE-20280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20280: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Fix possibility of deadlocking in refreshFileConnections when prefetch is > enabled > - > > Key: HBASE-20280 > URL: https://issues.apache.org/jira/browse/HBASE-20280 > Project: HBase > Issue Type: Bug > Components: BucketCache >Affects Versions: 2.0.0-beta-2, 1.4.2 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Fix For: 1.5.0, 1.4.4, 2.0.0 > > Attachments: HBASE-20280.master.001.patch > > > When prefetch on open is specified, there is a deadlocking case > where if the prefetch is cancelled, the PrefetchExecutor interrupts > the threads if necessary, when that happens in FileIOEngine, it > causes an ClosedByInterruptException which is a subclass of > ClosedChannelException. If we retry all ClosedChannelExceptions, > this will lock as this access is expected to be interrupted. > This change removes calling refreshFileConnections for > ClosedByInterruptExceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18876) Backup create command fails to take queue parameter as option
[ https://issues.apache.org/jira/browse/HBASE-18876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18876: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backup create command fails to take queue parameter as option > - > > Key: HBASE-18876 > URL: https://issues.apache.org/jira/browse/HBASE-18876 > Project: HBase > Issue Type: Bug >Reporter: Amit Kabra >Assignee: Amit Kabra >Priority: Major > Fix For: 2.0.0-alpha-4, 2.0.0 > > Attachments: HBASE-18876.patch > > > Backup help shows we can set queue using -q parameter. > -q Yarn queue name to run backup restore command on > But when we give ./hbase backup create full hdfs://localhost:8020/test/ -t > test1 -q hbase > It throws following error "Error when parsing command-line arguments: > Unrecognized option: -q" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18225) Fix findbugs regression calling toString() on an array
[
https://issues.apache.org/jira/browse/HBASE-18225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18225:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix findbugs regression calling toString() on an array
> --
>
> Key: HBASE-18225
> URL: https://issues.apache.org/jira/browse/HBASE-18225
> Project: HBase
> Issue Type: Bug
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: HBASE-18225.001.patch
>
>
> Looks like we got a findbugs warning as a result of HBASE-18166
> {code}
> diff --git
> a/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
>
> b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
> index 1d04944250..b7e0244aa2 100644
> ---
> a/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
> +++
> b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
> @@ -2807,8 +2807,8 @@ public class RSRpcServices implements
> HBaseRPCErrorHandler,
> HRegionInfo hri = rsh.s.getRegionInfo();
> // Yes, should be the same instance
> if (regionServer.getOnlineRegion(hri.getRegionName()) != rsh.r) {
> - String msg = "Region was re-opened after the scanner" + scannerName +
> " was created: "
> - + hri.getRegionNameAsString();
> + String msg = "Region has changed on the scanner " + scannerName + ":
> regionName="
> + + hri.getRegionName() + ", scannerRegionName=" + rsh.r;
> {code}
> Looks like {{hri.getRegionNameAsString()}} was unintentionally changed to
> {{hri.getRegionName()}}, [~syuanjiang]/[~stack]?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18475) MasterProcedureScheduler incorrectly passes null Procedure to table locking
[
https://issues.apache.org/jira/browse/HBASE-18475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18475:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> MasterProcedureScheduler incorrectly passes null Procedure to table locking
> ---
>
> Key: HBASE-18475
> URL: https://issues.apache.org/jira/browse/HBASE-18475
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 2.0.0-alpha-2, 2.0.0
>
> Attachments: HBASE-18475.0.patch
>
>
> Occasionally I get a series of these in tests during shutdown
> {code}
> 2017-07-27 16:24:26,774 DEBUG
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=37201]
> master.MasterRpcServices(1011): Checking to see if procedure is done
> procId=506
> 2017-07-27 16:24:26,777 INFO [main] client.HBaseAdmin$TableFuture(3591):
> Operation: CREATE, Table Name: default:foo failed with foo
> 2017-07-27 16:24:26,782 INFO
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=37201]
> master.HMaster$4(1755): Client=jenkins//172.26.21.67 create 'foo', {NAME =>
> 'family_1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> KEEP_DELETED_CELLS => 'FALSE', CACHE_DATA_ON_WRITE => 'false',
> DATA_BLOCK_ENCODING => 'NONE', TTL => 'FOREVER', MIN_VERSIONS => '0',
> REPLICATION_SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE =>
> 'false', IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'false',
> PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', CACHE_DATA_IN_L1
> => 'false', BLOCKCACHE => 'true', BLOCKSIZE => '65536'}
> 2017-07-27 16:24:26,884 DEBUG
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=37201]
> procedure2.ProcedureExecutor(792): Stored pid=507,
> state=RUNNABLE:CREATE_TABLE_PRE_OPERATION; CreateTableProcedure table=foo
> 2017-07-27 16:24:26,887 DEBUG
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=37201]
> master.MasterRpcServices(1011): Checking to see if procedure is done
> procId=507
> 2017-07-27 16:24:26,890 INFO [ProcExecWrkr-5]
> procedure2.ProcedureExecutor(1261): Rolled back pid=507, state=ROLLEDBACK,
> exception=org.apache.hadoop.hbase.TableExistsException via
> master-create-table:org.apache.hadoop.hbase.TableExistsException: foo;
> CreateTableProcedure table=foo exec-time=106msec
> 2017-07-27 16:24:26,890 WARN [ProcExecWrkr-5]
> procedure2.ProcedureExecutor$WorkerThread(1668): Worker terminating
> UNNATURALLY null
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.procedure.MasterProcedureScheduler.requireTableExclusiveLock(MasterProcedureScheduler.java:590)
> at
> org.apache.hadoop.hbase.master.procedure.MasterProcedureScheduler.access$300(MasterProcedureScheduler.java:106)
> at
> org.apache.hadoop.hbase.master.procedure.MasterProcedureScheduler$TableQueue.requireExclusiveLock(MasterProcedureScheduler.java:582)
> at
> org.apache.hadoop.hbase.master.procedure.MasterProcedureScheduler.doPoll(MasterProcedureScheduler.java:215)
> at
> org.apache.hadoop.hbase.master.procedure.MasterProcedureScheduler.dequeue(MasterProcedureScheduler.java:203)
> at
> org.apache.hadoop.hbase.procedure2.AbstractProcedureScheduler.poll(AbstractProcedureScheduler.java:145)
> at
> org.apache.hadoop.hbase.procedure2.AbstractProcedureScheduler.poll(AbstractProcedureScheduler.java:119)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1641)
> 2017-07-27 16:24:26,890 DEBUG [ProcExecWrkr-5]
> procedure2.ProcedureExecutor$WorkerThread(1670): Worker terminated.
> {code}
> Eventually all the workers are done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20290) Typo in enable_table_replication error message
[
https://issues.apache.org/jira/browse/HBASE-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20290:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Typo in enable_table_replication error message
> --
>
> Key: HBASE-20290
> URL: https://issues.apache.org/jira/browse/HBASE-20290
> Project: HBase
> Issue Type: Bug
> Components: shell
>Affects Versions: 1.2.6
>Reporter: Peter Somogyi
>Assignee: Gabor Bota
>Priority: Trivial
> Labels: beginner
> Fix For: 1.2.7
>
> Attachments: HBASE-20290.branch-1.2.001.patch
>
>
>
> Typo: comapred
> {noformat}
> hbase(main):020:0> enable_table_replication 'repl'
> ERROR: Table repl exists in peer cluster 1, but the table descriptors are not
> same when comapred with source cluster. Thus can not enable the table's
> replication switch.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail
[ https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20521: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script > run fail > --- > > Key: HBASE-20521 > URL: https://issues.apache.org/jira/browse/HBASE-20521 > Project: HBase > Issue Type: Bug > Components: mapreduce >Affects Versions: 2.0.0 > Environment: spark 2.2.1, hbase 2.0.0 >Reporter: Michael Jin >Assignee: Michael Jin >Priority: Major > Fix For: 3.0.0, 2.1.0, 2.0.1 > > Attachments: HBASE-20521.master.001.patch, > HBASE-20521.master.002.patch > > > HBASE-20295 fix null point exception of "conf" member variable, add > "context.getConfiguration()" in case when "conf" object was not been properly > initialized, and put it into the first priority checking sequence, this code > change affect user call "setConf" explicitly initialize "conf" object in > TableOutputFormat object, proposal to change checking sequence, use "conf" > object from "getConf" method first . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18590) branch-1.4 needs a Jenkins commit build job
[ https://issues.apache.org/jira/browse/HBASE-18590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18590: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > branch-1.4 needs a Jenkins commit build job > --- > > Key: HBASE-18590 > URL: https://issues.apache.org/jira/browse/HBASE-18590 > Project: HBase > Issue Type: Bug >Reporter: Jerry He >Assignee: Ted Yu >Priority: Critical > > The current HBase-1.4 job is actually branch-1. > https://builds.apache.org/job/HBase-1.4/ > Need a separate job for branch-1.4. And rename the current job to HBase-1.5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18292) Fix flaky test hbase.master.locking.TestLockProcedure#testLocalMasterLockRecovery()
[ https://issues.apache.org/jira/browse/HBASE-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18292: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Fix flaky test > hbase.master.locking.TestLockProcedure#testLocalMasterLockRecovery() > --- > > Key: HBASE-18292 > URL: https://issues.apache.org/jira/browse/HBASE-18292 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0.0-alpha-1 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0-alpha-2, 2.0.0 > > Attachments: HBASE-18292.master.001.patch > > > Assert before waitProcedure() assumes that procedure executer is still > running but this assumption is incorrect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20353) REST server startup fails
[
https://issues.apache.org/jira/browse/HBASE-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20353:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> REST server startup fails
> -
>
> Key: HBASE-20353
> URL: https://issues.apache.org/jira/browse/HBASE-20353
> Project: HBase
> Issue Type: Bug
> Components: REST
>Affects Versions: 2.0.0
>Reporter: Peter Somogyi
>Priority: Blocker
> Fix For: 2.0.0
>
>
> The rest server is not starting up using {{bin/hbase rest start}} and
> {{bin/hbase-daemon.sh start rest}} commands.
> {noformat}
> $ bin/hbase rest start
> 2018-04-05 15:29:36,905 INFO [main] RESTServer: * STARTING service
> 'RESTServer' *
> 2018-04-05 15:29:36,907 INFO [main] util.VersionInfo: HBase 2.0.0
> 2018-04-05 15:29:36,907 INFO [main] util.VersionInfo: Source code repository
> git://psomogyi-MBP.local/Users/peter.somogyi/Cloudera/hbase
> revision=c9f3eb00ab93d7b97de43c0bc3601371c77d0ba2
> 2018-04-05 15:29:36,907 INFO [main] util.VersionInfo: Compiled by
> peter.somogyi on Thu Apr 5 13:33:55 CEST 2018
> 2018-04-05 15:29:36,907 INFO [main] util.VersionInfo: From source with
> checksum 1231660fdac945689215f58245692691
> 2018-04-05 15:29:37,144 WARN [main] util.NativeCodeLoader: Unable to load
> native-hadoop library for your platform... using builtin-java classes where
> applicable
> 2018-04-05 15:29:37,524 INFO [main] metrics.MetricRegistries: Loaded
> MetricRegistries class
> org.apache.hadoop.hbase.metrics.impl.MetricRegistriesImpl
> 2018-04-05 15:29:37,620 INFO [main] util.log: Logging initialized @976ms
> 2018-04-05 15:29:37,765 INFO [main] http.HttpRequestLog: Http request log
> for http.requests.rest is not defined
> 2018-04-05 15:29:37,778 INFO [main] http.HttpServer: Added global filter
> 'safety' (class=org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter)
> 2018-04-05 15:29:37,779 INFO [main] http.HttpServer: Added global filter
> 'clickjackingprevention'
> (class=org.apache.hadoop.hbase.http.ClickjackingPreventionFilter)
> 2018-04-05 15:29:37,781 INFO [main] http.HttpServer: Added filter
> static_user_filter
> (class=org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter)
> to context rest
> 2018-04-05 15:29:37,781 INFO [main] http.HttpServer: Added filter
> static_user_filter
> (class=org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter)
> to context logs
> 2018-04-05 15:29:37,781 INFO [main] http.HttpServer: Added filter
> static_user_filter
> (class=org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter)
> to context static
> 2018-04-05 15:29:37,806 INFO [main] http.HttpServer: Jetty bound to port 8085
> 2018-04-05 15:29:37,807 INFO [main] server.Server: jetty-9.3.19.v20170502
> 2018-04-05 15:29:37,839 INFO [main] handler.ContextHandler: Started
> o.e.j.s.ServletContextHandler@2e8c1c9b{/logs,file:///Users/peter.somogyi/Cloudera/hbase/logs/,AVAILABLE}
> 2018-04-05 15:29:37,839 INFO [main] handler.ContextHandler: Started
> o.e.j.s.ServletContextHandler@449a4f23{/static,file:///Users/peter.somogyi/Cloudera/hbase/hbase-rest/target/hbase-webapps/static,AVAILABLE}
> 2018-04-05 15:29:37,937 INFO [main] handler.ContextHandler: Started
> o.e.j.w.WebAppContext@15d49048{/,file:///Users/peter.somogyi/Cloudera/hbase/hbase-rest/target/hbase-webapps/rest/,AVAILABLE}{file:/Users/peter.somogyi/Cloudera/hbase/hbase-rest/target/hbase-webapps/rest}
> 2018-04-05 15:29:37,946 INFO [main] server.AbstractConnector: Started
> ServerConnector@4ee203eb{HTTP/1.1,[http/1.1]}{0.0.0.0:8085}
> 2018-04-05 15:29:37,946 INFO [main] server.Server: Started @1303ms
> 2018-04-05 15:29:37,947 INFO [main] server.Server: jetty-9.3.19.v20170502
> 2018-04-05 15:29:37,955 WARN [main] security.SecurityHandler:
> ServletContext@o.e.j.s.ServletContextHandler@25084a1e{/,null,STARTING} has
> uncovered http methods for path: /*
> 2018-04-05 15:29:37,982 INFO [main] server.AbstractConnector: Started
> ServerConnector@49912c99{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
> Exception in thread "main" java.lang.NoSuchMethodError:
> javax.ws.rs.core.Application.getProperties()Ljava/util/Map;
> at
> org.glassfish.jersey.server.ApplicationHandler.(ApplicationHandler.java:331)
> at
> org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:392)
> at
> org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:177)
> at
> org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:369)
> at javax.servlet.GenericServlet.init(GenericServlet.java:244)
> at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:643)
> at
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:422)
>
[jira] [Issue Comment Deleted] (HBASE-19415) Backport HBASE-19056 to branch-1.x
[ https://issues.apache.org/jira/browse/HBASE-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19415: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-19056 to branch-1.x > -- > > Key: HBASE-19415 > URL: https://issues.apache.org/jira/browse/HBASE-19415 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 1.4.0, 1.5.0 >Reporter: Duo Zhang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20653) Add missing observer hooks for region server group to MasterObserver
[ https://issues.apache.org/jira/browse/HBASE-20653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20653: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Add missing observer hooks for region server group to MasterObserver > > > Key: HBASE-20653 > URL: https://issues.apache.org/jira/browse/HBASE-20653 > Project: HBase > Issue Type: Bug >Reporter: Ted Yu >Assignee: Nihal Jain >Priority: Major > Fix For: 3.0.0 > > Attachments: HBASE-20653.master.001.patch, > HBASE-20653.master.002.patch, HBASE-20653.master.003.patch, > HBASE-20653.master.004.patch > > > Currently the following region server group operations don't have > corresponding hook in MasterObserver : > * getRSGroupInfo > * getRSGroupInfoOfServer > * getRSGroupInfoOfTable > * listRSGroup > This JIRA is to > * add them to MasterObserver > * add pre/post hook calls in RSGroupAdminEndpoint thru > master.getMasterCoprocessorHost for the above operations > * add corresponding tests to TestRSGroups (in similar manner to that of > HBASE-20627) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20581) HBase book documentation wrong for REST operations on schema endpoints
[
https://issues.apache.org/jira/browse/HBASE-20581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20581:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HBase book documentation wrong for REST operations on schema endpoints
> --
>
> Key: HBASE-20581
> URL: https://issues.apache.org/jira/browse/HBASE-20581
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Kevin Risden
>Assignee: Josh Elser
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HBASE-20581.001.patch
>
>
> On [https://hbase.apache.org/book.html#_using_rest_endpoints]
> The documentation states that to update a table schema (the configuration for
> a column family), the {{PUT}} HTTP verb will update the current configuration
> with the "fragment" of configuration provided, while the {{POST}} HTTP verb
> will replace the current configuration with whatever is provided.
> In reality, the opposite is true: {{POST}} updates the configuration, {{PUT}}
> replaces. The old javadoc for the o.a.h.h.rest package got it right, but the
> entry on the HBase book transposed this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18506) java.lang.AbstractMethodError in hbase REST server
[
https://issues.apache.org/jira/browse/HBASE-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18506:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> java.lang.AbstractMethodError in hbase REST server
> --
>
> Key: HBASE-18506
> URL: https://issues.apache.org/jira/browse/HBASE-18506
> Project: HBase
> Issue Type: Bug
> Components: REST
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
>Priority: Blocker
> Fix For: 3.0.0
>
>
> Just run it this one while testing some scripts. Basically any call to
> service will end up with 500 error. After some checking it looks like we have
> some issues with dependencies incompatibility.
> Here is more details:
> {code}
> Stack trace:
> 2017-08-02 20:46:25,407 WARN [qtp422330142-30] servlet.ServletHandler: Error
> for /status/cluster
> java.lang.AbstractMethodError:
> javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;
> at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:119)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:298)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
> at
> org.apache.hadoop.hbase.rest.filter.GzipFilter.doFilter(GzipFilter.java:77)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
> 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:1160)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.server.Server.handle(Server.java:518)
> at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
> at
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
> at
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> and here are suspects from lib dir
> {code}
> $ grep -r "UriBuilder" .
> Binary file ./javax.ws.rs-api-2.0.1.jar matches
> Binary file ./jersey-common-2.25.1.jar matches
> Binary file ./jersey-core-1.9.jar matches
> {code}
> I have also checked hbase-1.2.6 we have only jersey-core-1.9.jar there
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20124) Make hbase-spark module work with hadoop3
[
https://issues.apache.org/jira/browse/HBASE-20124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20124:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Make hbase-spark module work with hadoop3
> -
>
> Key: HBASE-20124
> URL: https://issues.apache.org/jira/browse/HBASE-20124
> Project: HBase
> Issue Type: Bug
> Components: dependencies, hadoop3, spark
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 20124.v1.txt, 20124.v2.txt, 20124.v3.txt
>
>
> The following error can be observed when running tests in hbase-spark module
> against hadoop3:
> {code}
> HBaseDStreamFunctionsSuite:
> *** RUN ABORTED ***
> java.lang.NoClassDefFoundError: org/apache/hadoop/ipc/ExternalCall
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getStorageDirs(FSNamesystem.java:1464)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getNamespaceDirs(FSNamesystem.java:1444)
> at
> org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:939)
> at
> org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:815)
> at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:746)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:668)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:640)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:979)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:859)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:853)
> ...
> Cause: java.lang.ClassNotFoundException: org.apache.hadoop.ipc.ExternalCall
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getStorageDirs(FSNamesystem.java:1464)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getNamespaceDirs(FSNamesystem.java:1444)
> at
> org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:939)
> at
> org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:815)
> at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:746)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:668)
> {code}
> The dependency tree shows mixture of hadoop 2.7.4 and hadoop3 for the
> hbase-spark module.
> This should be addressed by adding proper profile in pom.xml
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19363) Tests under TestCheckAndMutate are identical
[ https://issues.apache.org/jira/browse/HBASE-19363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19363: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Tests under TestCheckAndMutate are identical > > > Key: HBASE-19363 > URL: https://issues.apache.org/jira/browse/HBASE-19363 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0.0-alpha-4 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Minor > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-19363.master.001.patch > > > TestCheckAndMutate has 2 tests and the content is the same in both. > Originally testCheckAndMutate and > testCheckAndMutateUsingNewComparisonOperatorInstead was different in calling > table.checkAndMutate with CompareFilter.CompareOp.EQUAL vs. > CompareOperator.EQUAL. > Since the implementations in HTable use the string value of the enums these > were were identical before. > Remove one of the tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18071) Fix flaky test TestStochasticLoadBalancer#testBalanceCluster
[ https://issues.apache.org/jira/browse/HBASE-18071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18071: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Fix flaky test TestStochasticLoadBalancer#testBalanceCluster > > > Key: HBASE-18071 > URL: https://issues.apache.org/jira/browse/HBASE-18071 > Project: HBase > Issue Type: Bug > Components: Balancer >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-18071.master.001.patch > > > Fix flaky test TestStochasticLoadBalancer#testBalanceCluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18325) Disable flakey TestMasterProcedureWalLease
[ https://issues.apache.org/jira/browse/HBASE-18325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18325: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Disable flakey TestMasterProcedureWalLease > -- > > Key: HBASE-18325 > URL: https://issues.apache.org/jira/browse/HBASE-18325 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18997) Remove the redundant methods in RegionInfo
[
https://issues.apache.org/jira/browse/HBASE-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18997:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Remove the redundant methods in RegionInfo
> --
>
> Key: HBASE-18997
> URL: https://issues.apache.org/jira/browse/HBASE-18997
> Project: HBase
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 2.0.0-alpha-4, 2.0.0
>
> Attachments: HBASE-18997.v0.patch, HBASE-18997.v1.patch,
> HBASE-18997.v1.patch
>
>
> The {{isSystemTable}} is short cut to {{TableName}}, and the {{isMetaTable}}
> is always equal with {{isMetaRegion}}. Our IA.Public interface should be
> minimalist
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19466) Rare failure in TestScannerCursor
[ https://issues.apache.org/jira/browse/HBASE-19466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19466: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Rare failure in TestScannerCursor > - > > Key: HBASE-19466 > URL: https://issues.apache.org/jira/browse/HBASE-19466 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Andrew Purtell >Priority: Minor > > I think we just need to increase the timeout interval to deal with occasional > slowdowns on test executors. 1998 ms is a pretty short timeout. > By the way "rpcTimetout" in the exception message is a misspelling. > [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 37.412 s <<< FAILURE! - in > org.apache.hadoop.hbase.regionserver.TestScannerCursor > [ERROR] > testHeartbeatWithSparseFilter(org.apache.hadoop.hbase.regionserver.TestScannerCursor) > Time elapsed: 35.604 s <<< ERROR! > org.apache.hadoop.hbase.client.RetriesExhaustedException: > Failed after attempts=36, exceptions: > Thu Dec 07 22:27:16 UTC 2017, null, java.net.SocketTimeoutException: > callTimeout=4000, callDuration=4108: Call to > ip-172-31-47-35.us-west-2.compute.internal/172.31.47.35:35690 failed on local > exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=52, > waitTime=2002, rpcTimetout=1998 row '' on table 'TestScannerCursor' at > region=TestScannerCursor,,1512685598567.1d4e59215a881d6ccbd0b5b5bdec5587., > hostname=ip-172-31-47-35.us-west-2.compute.internal,35690,1512685593244, > seqNum=2 > at > org.apache.hadoop.hbase.regionserver.TestScannerCursor.testHeartbeatWithSparseFilter(TestScannerCursor.java:154) > Caused by: java.net.SocketTimeoutException: callTimeout=4000, > callDuration=4108: Call to > ip-172-31-47-35.us-west-2.compute.internal/172.31.47.35:35690 failed on local > exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=52, > waitTime=2002, rpcTimetout=1998 row '' on table 'TestScannerCursor' at > region=TestScannerCursor,,1512685598567.1d4e59215a881d6ccbd0b5b5bdec5587., > hostname=ip-172-31-47-35.us-west-2.compute.internal,35690,1512685593244, > seqNum=2 > Caused by: java.io.IOException: Call to > ip-172-31-47-35.us-west-2.compute.internal/172.31.47.35:35690 failed on local > exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=52, > waitTime=2002, rpcTimetout=1998 > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=52, > waitTime=2002, rpcTimetout=1998 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18099) FlushSnapshotSubprocedure should wait for concurrent Region#flush() to finish
[
https://issues.apache.org/jira/browse/HBASE-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18099:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> FlushSnapshotSubprocedure should wait for concurrent Region#flush() to finish
> -
>
> Key: HBASE-18099
> URL: https://issues.apache.org/jira/browse/HBASE-18099
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Fix For: 1.4.0, 2.0.0
>
> Attachments: 18099.v1.txt, 18099.v2.txt, 18099.v3.txt, 18099.v4.txt
>
>
> In the following thread:
> http://search-hadoop.com/m/HBase/YGbbMXkeHlI9zo
> Jacob described the scenario where data from certain region were missing in
> the snapshot.
> Here was related region server log:
> https://pastebin.com/1ECXjhRp
> He pointed out that concurrent flush from MemStoreFlusher.1 thread was not
> initiated from the thread pool for snapshot.
> In RegionSnapshotTask#call() method there is this:
> {code}
> region.flush(true);
> {code}
> The return value is not checked.
> In HRegion#flushcache(), Result.CANNOT_FLUSH may be returned due to:
> {code}
> String msg = "Not flushing since "
> + (writestate.flushing ? "already flushing"
> : "writes not enabled");
> {code}
> This implies that FlushSnapshotSubprocedure may incorrectly skip waiting for
> the concurrent flush to complete.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20785) NPE getting metrics in PE testing scans
[ https://issues.apache.org/jira/browse/HBASE-20785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20785: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > NPE getting metrics in PE testing scans > --- > > Key: HBASE-20785 > URL: https://issues.apache.org/jira/browse/HBASE-20785 > Project: HBase > Issue Type: Bug > Components: Performance >Affects Versions: 1.4.4 >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.1.0, 1.3.3, 1.4.6, 2.0.2 > > Attachments: HBASE-20785.branch-1.4.001.patch, > HBASE-20785.branch-1.4.001.patch, HBASE-20785.branch-1.4.001.patch > > > Comparing scans using PE. In branch-1 at least, I was getting an NPE when we > tried to use a null metrics instance. Seems transient around startup. > One-liner patch coming. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19169) Rowcounter job fails against hadoop3 beta1
[
https://issues.apache.org/jira/browse/HBASE-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19169:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Rowcounter job fails against hadoop3 beta1
> --
>
> Key: HBASE-19169
> URL: https://issues.apache.org/jira/browse/HBASE-19169
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
>
> I got the following error running rowcounter against hadoop3 beta1 based on
> commit a9f0c5d4e2c85c1faae1b4b277e3c290c8b81d2a :
> {code}
> 2017-11-03 17:10:59,583 INFO [main] mapreduce.Job: Task Id :
> attempt_1509641483571_0006_m_29_1, Status : FAILED
> Error: java.lang.ArrayIndexOutOfBoundsException: 2
> at
> org.apache.hadoop.hbase.mapreduce.TableSplit$Version.fromCode(TableSplit.java:77)
> at
> org.apache.hadoop.hbase.mapreduce.TableSplit.readFields(TableSplit.java:285)
> at
> org.apache.hadoop.io.serializer.WritableSerialization$WritableDeserializer.deserialize(WritableSerialization.java:71)
> at
> org.apache.hadoop.io.serializer.WritableSerialization$WritableDeserializer.deserialize(WritableSerialization.java:42)
> at org.apache.hadoop.mapred.MapTask.getSplitDetails(MapTask.java:372)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:760)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:174)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:168)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20096) Missing version warning for exec-maven-plugin in hbase-shaded-check-invariants
[
https://issues.apache.org/jira/browse/HBASE-20096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20096:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Missing version warning for exec-maven-plugin in hbase-shaded-check-invariants
> --
>
> Key: HBASE-20096
> URL: https://issues.apache.org/jira/browse/HBASE-20096
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Andrew Purtell
>Priority: Minor
>
> Reported by [~dbist13]:
> Affects branch-1 and branch-1.4
> {noformat}
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.hbase:hbase-shaded-check-invariants:pom:1.5.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for
> org.codehaus.mojo:exec-maven-plugin is missing. @
> org.apache.hbase:hbase-shaded-check-invariants:[unknown-version],
> /Users/apurtell/src/hbase/hbase-shaded/hbase-shaded-check-invariants/pom.xml,
> line 161, column 15
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18586) Multiple column families - scan performance
[ https://issues.apache.org/jira/browse/HBASE-18586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18586: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Multiple column families - scan performance > --- > > Key: HBASE-18586 > URL: https://issues.apache.org/jira/browse/HBASE-18586 > Project: HBase > Issue Type: Bug > Components: scan >Reporter: PS0618 >Priority: Major > > I have 2 HBase tables - one with a single column family, and other has 4 > column families. Both tables are keyed by same rowkey, and the column > families all have a single column qualifier each, with a json string as value > (each json payload is about 10-20K in size). All column families use > fast-diff encoding and gzip compression. > After loading about 60MM rows to each table, a scan test on (any) single > column family in the 2nd table takes 4x the time to scan the single column > family from the 1st table. In both cases, the scanner is bounded by a start > and stop key to scan 1MM rows. Performance did not change much even after > running a major compaction on both tables. > Though HBase doc and other tech forums recommend not using more than 1 column > family per table, nothing I have read so far suggests scan performance will > linearly degrade based on number of column families. Has anyone else > experienced this, and is there a simple explanation for this? > To note, the reason second table has 4 column families is even though I only > scan one column family at a time now, there are requirements to scan multiple > column families from that table given a set of rowkeys. > Thanks for any insight into the performance question. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19181) LogRollBackupSubprocedure will fail if we use AsyncFSWAL instead of FSHLog
[ https://issues.apache.org/jira/browse/HBASE-19181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19181: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > LogRollBackupSubprocedure will fail if we use AsyncFSWAL instead of FSHLog > -- > > Key: HBASE-19181 > URL: https://issues.apache.org/jira/browse/HBASE-19181 > Project: HBase > Issue Type: Bug > Components: backuprestore >Reporter: Duo Zhang >Assignee: Vladimir Rodionov >Priority: Major > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-19181-v1.patch, HBASE-19181-v2.patch > > > In the RSRollLogTask it will cast a WAL to FSHLog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19040) CP service exec broken for older clients after PB namespace addition
[
https://issues.apache.org/jira/browse/HBASE-19040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19040:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> CP service exec broken for older clients after PB namespace addition
>
>
> Key: HBASE-19040
> URL: https://issues.apache.org/jira/browse/HBASE-19040
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors, Protobufs
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Blocker
>
> Was investigating an upgrade failure at dayjob. The "old" version did not
> include HBASE-14077 while the new version did include HBASE-14077.
> After the servers have been upgraded, the clients which try to execute CP
> calls will begin to fail with a message such as:
> {noformat}
> $ hbase(main):001:0> user_permission
> User
> Namespace,Table,Family,Qualifier:Permission
> ERROR: org.apache.hadoop.hbase.exceptions.UnknownProtocolException: No
> registered coprocessor service found for name AccessControlService in region
> hbase:acl,,1508228211139.0ef76894681187f0ef958e78aed64d30.
> at
> org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7829)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1980)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1962)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2150)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
> {noformat}
> The funny part is that the Region actually has a CP registered under the name
> {{hbase.pb.AccessControlService}}, but the client asks for one under
> {{AccessControlService}}.
> I think the easy fix is to deploy the CP under both names while HBase
> services support client backwards compatibility with 1.x clients.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18235) LoadBalancer.BOGUS_SERVER_NAME should not have a bogus hostname
[ https://issues.apache.org/jira/browse/HBASE-18235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18235: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > LoadBalancer.BOGUS_SERVER_NAME should not have a bogus hostname > --- > > Key: HBASE-18235 > URL: https://issues.apache.org/jira/browse/HBASE-18235 > Project: HBase > Issue Type: Bug >Reporter: Francis Liu >Assignee: Francis Liu >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-18235.patch > > > The original patch used localhost to have assignment fail fast. Avoiding > misleading DNS exceptions, delays due to dns lookup, etc. > Was wondering what the reason was for changing it? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18928) Backup delete command shows wrong number of deletes requested
[
https://issues.apache.org/jira/browse/HBASE-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18928:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Backup delete command shows wrong number of deletes requested
> -
>
> Key: HBASE-18928
> URL: https://issues.apache.org/jira/browse/HBASE-18928
> Project: HBase
> Issue Type: Bug
>Reporter: Amit Kabra
>Assignee: Amit Kabra
>Priority: Minor
> Fix For: 2.0.0-alpha-4, 2.0.0
>
> Attachments: HBASE-18928.patch, HBASE-18928.v2.patch.txt
>
>
> {code}./hbase backup delete backup_1506934800496 backup_1506934749163{code}
> 2017-10-02 14:55:39,788 WARN [main] util.NativeCodeLoader: Unable to load
> native-hadoop library for your platform... using builtin-java classes where
> applicable
> 2017-10-02 14:55:40,151 WARN [main] shortcircuit.DomainSocketFactory: The
> short-circuit local reads feature cannot be used because libhadoop cannot be
> loaded.
> Please make sure that backup is enabled on the cluster. To enable backup, in
> hbase-site.xml, set:
> hbase.backup.enable=true
> hbase.master.logcleaner.plugins=YOUR_PLUGINS,org.apache.hadoop.hbase.backup.master.BackupLogCleaner
> hbase.procedure.master.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.master.LogRollMasterProcedureManager
> hbase.procedure.regionserver.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.regionserver.LogRollRegionServerProcedureManager
> and restart the cluster
> 2017-10-02 14:55:40,328 INFO [main] metrics.MetricRegistries: Loaded
> MetricRegistries class
> org.apache.hadoop.hbase.metrics.impl.MetricRegistriesImpl
> 2017-10-02 14:55:41,876 INFO [main] impl.BackupAdminImpl: Deleting backup
> backup_1506934749163 ...
> 2017-10-02 14:55:41,970 INFO [main] util.BackupUtils: No data has been found
> in hdfs://localhost:8020/test/backup_1506934749163/default/raj22.
> 2017-10-02 14:55:41,998 INFO [main] impl.BackupAdminImpl: Delete backup
> backup_1506934749163 completed.
> *Deleted 1 backups. Total requested: 3*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20341) Nothing in refguide on hedgedreads; fix
[ https://issues.apache.org/jira/browse/HBASE-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20341: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Nothing in refguide on hedgedreads; fix > --- > > Key: HBASE-20341 > URL: https://issues.apache.org/jira/browse/HBASE-20341 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: stack >Assignee: Wei-Chiu Chuang >Priority: Critical > > There are even metrics from HBASE-12220 that expose counts. Talk them up and > hedged reads in refguide. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20394) HBase over rides the value of HBASE_OPTS (if any) set by client
[
https://issues.apache.org/jira/browse/HBASE-20394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20394:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HBase over rides the value of HBASE_OPTS (if any) set by client
> ---
>
> Key: HBASE-20394
> URL: https://issues.apache.org/jira/browse/HBASE-20394
> Project: HBase
> Issue Type: Bug
> Components: Operability
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-20394.master.001.patch
>
>
> Currently HBase will over ride the value of HBASE_OPTS (if any) set by user
> {code:java}
> export HBASE_OPTS="-XX:+UseConcMarkSweepGC" {code}
> [See
> hbase-env.sh|https://github.com/apache/hbase/blob/68726b0ee3ef3eb52d32481444e64236c5a9e733/conf/hbase-env.sh#L43]
>
> But, a user may have the following set in his environment:
> {code:java}
> HBASE_OPTS="-Xmn512m"{code}
> While starting the processes, HBase will internally over-ride the existing
> HBASE_OPTS value with the one set in hbase-env.sh
>
> Instead of over-riding we can have the following in hbase-env.sh:
> {code:java}
> export HBASE_OPTS="$HBASE_OPTS -XX:+UseConcMarkSweepGC"{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19964) TestWriteHeavyIncrementObserver fails
[ https://issues.apache.org/jira/browse/HBASE-19964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19964: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TestWriteHeavyIncrementObserver fails > - > > Key: HBASE-19964 > URL: https://issues.apache.org/jira/browse/HBASE-19964 > Project: HBase > Issue Type: Bug > Components: test >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-19964-addendum.patch, HBASE-19964.patch > > > https://builds.apache.org/job/HBASE-Flaky-Tests/25704/artifact/hbase-examples/target/surefire-reports/org.apache.hadoop.hbase.coprocessor.example.TestWriteHeavyIncrementObserver-output.txt/*view*/ > I could reproduce it locally. Let me dig more. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18924) Backport HBASE-18568 (Correct metric of numRegions) to branch-1.2 and branch-1.3
[ https://issues.apache.org/jira/browse/HBASE-18924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18924: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-18568 (Correct metric of numRegions) to branch-1.2 and > branch-1.3 > > > Key: HBASE-18924 > URL: https://issues.apache.org/jira/browse/HBASE-18924 > Project: HBase > Issue Type: Bug > Components: metrics >Affects Versions: 1.2.6 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Critical > Fix For: 1.3.2, 1.2.7 > > Attachments: HBASE-18924.branch-1.2.001.patch, > HBASE-18924.branch-1.2.002.patch, HBASE-18924.branch-1.3.002.patch > > > HBASE-18568 corrects an issue with metrics which leads to memory leak. We > should apply this fix to branch-1.2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19593) Possible NPE if wal is closed during waledit append.
[
https://issues.apache.org/jira/browse/HBASE-19593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19593:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Possible NPE if wal is closed during waledit append.
>
>
> Key: HBASE-19593
> URL: https://issues.apache.org/jira/browse/HBASE-19593
> Project: HBase
> Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19593.patch
>
>
> There is a possible NPE when a wal is closed during waledit append because of
> not setting write entry to the wal key. Here is the code we are not setting
> write entry to wal key when when wal is closed.
> {noformat}
> if (this.closed) {
> throw new IOException(
> "Cannot append; log is closed, regionName = " +
> hri.getRegionNameAsString());
> }
> MutableLong txidHolder = new MutableLong();
> MultiVersionConcurrencyControl.WriteEntry we = key.getMvcc().begin(() -> {
> txidHolder.setValue(ringBuffer.next());
> });
> long txid = txidHolder.longValue();
> try (TraceScope scope = TraceUtil.createTrace(implClassName + ".append"))
> {
> FSWALEntry entry = new FSWALEntry(txid, key, edits, hri, inMemstore);
> entry.stampRegionSequenceId(we);
> ringBuffer.get(txid).load(entry);
> } finally {
> ringBuffer.publish(txid);
> }
> return txid;
> {noformat}
> But on failure complete on mvcc will be called with nulll write entry cause
> NPE.
> {noformat}
> WriteEntry writeEntry = null;
> try {
> long txid = this.wal.append(this.getRegionInfo(), walKey, walEdit,
> true);
> // Call sync on our edit.
> if (txid != 0) {
> sync(txid, durability);
> }
> writeEntry = walKey.getWriteEntry();
> } catch (IOException ioe) {
> if (walKey != null) {
> mvcc.complete(walKey.getWriteEntry());
> }
> throw ioe;
> }
> {noformat}
> We are able to reproduce with mocking in one of the phoenix test cases to
> test wal replay.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19184) clean up nightly source artifact test to match expectations from switch to git-archive
[ https://issues.apache.org/jira/browse/HBASE-19184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19184: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > clean up nightly source artifact test to match expectations from switch to > git-archive > -- > > Key: HBASE-19184 > URL: https://issues.apache.org/jira/browse/HBASE-19184 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1, 1.1.13, 2.0.0 > > Attachments: HBASE-19184.0.patch, HBASE-19184.1.patch > > > HBASE-19152 changed recommended way of building RC source artifacts to rely > on git archive instead of the maven assembly plugin. > update nightly test to match those expectations.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master
[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19392: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master > - > > Key: HBASE-19392 > URL: https://issues.apache.org/jira/browse/HBASE-19392 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 3.0.0, 2.0.0-alpha-4 >Reporter: huaxiang sun >Assignee: stack >Priority: Minor > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: HBASE-19392-master-v001.patch > > > Please see the flakey test list. > https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html > client.TestReplicaWithCluster 96.7% (29 / 30) 29 / 0 / 0 > show/hide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20058) improper quoting in presplitting command docs
[
https://issues.apache.org/jira/browse/HBASE-20058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20058:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> improper quoting in presplitting command docs
> -
>
> Key: HBASE-20058
> URL: https://issues.apache.org/jira/browse/HBASE-20058
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Mike Drob
>Assignee: maoling
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20058-master-v0.patch
>
>
> http://hbase.apache.org/book.html#tricks.pre-split
> {code}
> hbase>create 't1','f',SPLITS => ['10','20',30']
> {code}
> Missing a quote before the 30./
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19713) Enable TestInterfaceAudienceAnnotations
[ https://issues.apache.org/jira/browse/HBASE-19713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19713: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Enable TestInterfaceAudienceAnnotations > --- > > Key: HBASE-19713 > URL: https://issues.apache.org/jira/browse/HBASE-19713 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-19713.branch-2.v0.patch, > HBASE-19713.branch-2.v1.patch, HBASE-19713.branch-2.v2.patch, > HBASE-19713.v0.patch > > > Make sure TestInterfaceAudienceAnnotations pass before 2.0 release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19583) update RM list to remove EOM versions
[ https://issues.apache.org/jira/browse/HBASE-19583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19583: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > update RM list to remove EOM versions > - > > Key: HBASE-19583 > URL: https://issues.apache.org/jira/browse/HBASE-19583 > Project: HBase > Issue Type: Bug > Components: community, documentation >Reporter: Appy >Assignee: Sean Busbey >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-19583.patch > > > wdys [~enis] [~ndimiduk]? > This needs updating too - http://hbase.apache.org/book.html#_release_managers. > I think we should mention RMs for all branches, even eols, if only in other > table. Good way to recognize past efforts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19019:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.branch-1.2.dummy.patch,
> HBASE-19019.branch-1.2.dummy.v1.patch, HBASE-19019.branch-1.2.dummy.v2.patch,
> HBASE-19019.branch-1.2.no_para.patch, HBASE-19019.branch-1.2.no_para.patch,
> HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18472) Add guava license and update supplemental-models.xml
[
https://issues.apache.org/jira/browse/HBASE-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18472:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Add guava license and update supplemental-models.xml
>
>
> Key: HBASE-18472
> URL: https://issues.apache.org/jira/browse/HBASE-18472
> Project: HBase
> Issue Type: Bug
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Yi Liang
>Assignee: Yi Liang
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-18472-master-v1.patch
>
>
> When I run mvn clean install -DskipTests on my local machine, lt always shows
> error below
> {quote}
> WARNING] Rule 0: org.apache.maven.plugins.enforcer.EvaluateBeanshell failed
> with message:
> License errors detected, for more detail find ERROR in
> hbase-assembly/target/maven-shared-archive-resources/META-INF/LICENSE
> Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce
> (check-aggregate-license) on project hbase-assembly: Some Enforcer rules have
> failed. Look above for specific messages explaining why the rule failed.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19396) Fix flaky test TestHTableMultiplexerFlushCache
[ https://issues.apache.org/jira/browse/HBASE-19396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19396: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Fix flaky test TestHTableMultiplexerFlushCache > -- > > Key: HBASE-19396 > URL: https://issues.apache.org/jira/browse/HBASE-19396 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 1.5.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0 > > Attachments: HBASE-19396.branch-1.001.patch, > HBASE-19396.branch-1.001.patch > > > [INFO] Running org.apache.hadoop.hbase.client.TestHTableMultiplexerFlushCache > [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 36.67 > s <<< FAILURE! - in > org.apache.hadoop.hbase.client.TestHTableMultiplexerFlushCache > [ERROR] > testOnRegionMove(org.apache.hadoop.hbase.client.TestHTableMultiplexerFlushCache) > Time elapsed: 4.644 s <<< FAILURE! > java.lang.AssertionError: Did not find a new RegionServer to use > at > org.apache.hadoop.hbase.client.TestHTableMultiplexerFlushCache.testOnRegionMove(TestHTableMultiplexerFlushCache.java:160) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18014) A case of Region remain unassigned when table enabled
[
https://issues.apache.org/jira/browse/HBASE-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18014:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> A case of Region remain unassigned when table enabled
> -
>
> Key: HBASE-18014
> URL: https://issues.apache.org/jira/browse/HBASE-18014
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.4.0, 1.1.10
>Reporter: Allan Yang
>Assignee: Allan Yang
>Priority: Major
> Fix For: 1.4.0, 1.3.2
>
> Attachments: HBASE-18014-branch-1.patch, HBASE-18014-branch-1.v2.patch
>
>
> Reproduce procedure:
> 1. Create a table, say the regions of this table are opened on RS1
> 2. Disable this table
> 3. Abort RS1 and wait for SSH to complete
> 4. Wait for a while, RS1 will be deleted from processedServers(a HashMap in
> {{RegionState}} to store processed dead servers)
> 5. Enable the table, then the region of the table will remain unassigned
> until master restarts.
> Why?
> When assigning regions after the table enabled, AssignmentManager will check
> whether those regions are on servers which are dead but not processed, since
> RS1 already have deleted from the map of 'processedServers'. Then the
> AssignmentManager think this region is on a dead but not processed server. So
> it will skip assign, let the region be handled by SSH.
> {code:java}
> case OFFLINE:
> if (useZKForAssignment
> && regionStates.isServerDeadAndNotProcessed(sn)
> && wasRegionOnDeadServerByMeta(region, sn)) {
> if (!regionStates.isRegionInTransition(region)) {
> LOG.info("Updating the state to " + State.OFFLINE + " to allow to
> be reassigned by SSH");
> regionStates.updateRegionState(region, State.OFFLINE);
> }
> LOG.info("Skip assigning " + region.getRegionNameAsString()
> + ", it is on a dead but not processed yet server: " + sn);
> return null;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18851) LICENSE failure after HADOOP-14799 with Hadoop 3
[
https://issues.apache.org/jira/browse/HBASE-18851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18851:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> LICENSE failure after HADOOP-14799 with Hadoop 3
>
>
> Key: HBASE-18851
> URL: https://issues.apache.org/jira/browse/HBASE-18851
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: 2.0.0-alpha-4, 2.0.0
>
> Attachments: HBASE-18851.001.branch-2.patch
>
>
> Building against a new hadoop-3 snapshot nets a failure in generating the
> LICENSE file for hbase-assembly.
> This is because hadoop-auth's dependency on
> com.nimbusds:nimbus-jose-jwt:jar:4.41.1 brings in org.ow2.asm:asm:jar:5.0.4
> which is licensed was 3-clause BSD but just states the license as "BSD". This
> breaks our parsing.
> Simple change to add "BSD" to our list {{non_aggregate_fine}} in
> {{LICENSE.vm}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18464) Backport HBASE-17131 (Avoid livelock caused by HRegion#processRowsWithLocks) into branch-1.3 and branch-1.2
[ https://issues.apache.org/jira/browse/HBASE-18464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18464: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-17131 (Avoid livelock caused by HRegion#processRowsWithLocks) > into branch-1.3 and branch-1.2 > --- > > Key: HBASE-18464 > URL: https://issues.apache.org/jira/browse/HBASE-18464 > Project: HBase > Issue Type: Bug >Affects Versions: 1.3.1, 1.2.6 >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Major > > see HBASE-17131 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19813) clone_snapshot fails with region failing to open when RS group feature is enabled
[
https://issues.apache.org/jira/browse/HBASE-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19813:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> clone_snapshot fails with region failing to open when RS group feature is
> enabled
> -
>
> Key: HBASE-19813
> URL: https://issues.apache.org/jira/browse/HBASE-19813
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
>
> The following scenario came from support case.
> In cluster 1, create RS group rsg. Move table to rsg group.
> Take snapshot of the table and copy the snapshot to cluster 2 where there is
> no group called rsg.
> Cloning snapshot to table new_t4 on cluster 2 fails :
> {code}
> 2018-01-09 11:45:30,468 INFO [RestoreSnapshot-pool68-t1]
> regionserver.HRegion: Closed
> new_t4,,1514454789243.a6173d2955182ac5bde208301681c6af.
> 2018-01-09 11:45:30,468 INFO [MASTER_TABLE_OPERATIONS-shubh1-1:16000-0]
> snapshot.CloneSnapshotHandler: Clone snapshot=snap_t3 on table=new_t4
> completed!
> 2018-01-09 11:45:30,492 INFO [MASTER_TABLE_OPERATIONS-shubh1-1:16000-0]
> hbase.MetaTableAccessor: Added 1
> 2018-01-09 11:45:30,492 WARN [MASTER_TABLE_OPERATIONS-shubh1-1:16000-0]
> rsgroup.RSGroupBasedLoadBalancer: Group for table new_t4 is null
> 2018-01-09 11:45:30,492 DEBUG [MASTER_TABLE_OPERATIONS-shubh1-1:16000-0]
> rsgroup.RSGroupBasedLoadBalancer: Group Information found to be null. Some
> regions might be unassigned.
> 2018-01-09 11:45:30,492 WARN [MASTER_TABLE_OPERATIONS-shubh1-1:16000-0]
> master.RegionStates: Failed to open/close a6173d2955182ac5bde208301681c6af on
> null, set to FAILED_OPEN
> {code}
> Here is related code from RSGroupBasedLoadBalancer:
> {code}
> List candidateList = filterOfflineServers(info, servers);
> for (RegionInfo region : regionList) {
> currentAssignmentMap.put(region, regions.get(region));
> }
> if(candidateList.size() > 0) {
> assignments.putAll(this.internalBalancer.retainAssignment(
> currentAssignmentMap, candidateList));
> {code}
> candidateList is empty for table new_t4, leaving region for the table in
> FAILED_OPEN state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20497) The getRecoveredQueueStartPos always return 0 in RecoveredReplicationSourceShipper
[ https://issues.apache.org/jira/browse/HBASE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20497: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > The getRecoveredQueueStartPos always return 0 in > RecoveredReplicationSourceShipper > -- > > Key: HBASE-20497 > URL: https://issues.apache.org/jira/browse/HBASE-20497 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.1.0 >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20497.v1.patch > > > See > https://issues.apache.org/jira/browse/HBASE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16454240#comment-16454240 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18262) name of parameter quote need update in hbase-default.xml
[ https://issues.apache.org/jira/browse/HBASE-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18262: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > name of parameter quote need update in hbase-default.xml > > > Key: HBASE-18262 > URL: https://issues.apache.org/jira/browse/HBASE-18262 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Dongtao Zhang >Assignee: Dongtao Zhang >Priority: Minor > Fix For: 2.0.0-alpha-2, 2.0.0 > > Attachments: HBASE-18262-v001.patch > > > In description of parameter "hbase.zookeeper.quorum", old name > "hbase.zookeeper.clientPort " should be replaced to > "hbase.zookeeper.property.clientPort". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20560) Revisit the TestReplicationDroppedTables ut
[ https://issues.apache.org/jira/browse/HBASE-20560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20560: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Revisit the TestReplicationDroppedTables ut > --- > > Key: HBASE-20560 > URL: https://issues.apache.org/jira/browse/HBASE-20560 > Project: HBase > Issue Type: Bug >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0, 2.2.0 > > Attachments: HBASE-20560.patch, HBASE-20560.patch > > > After HBASE-20475, the ut TestReplicationDroppedTables has been more stable > now, but still failed in few times.. > Checked the code again, I found the problems: > 1. > https://issues.apache.org/jira/browse/HBASE-20475?focusedCommentId=16465759=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16465759 > 2. > https://issues.apache.org/jira/browse/HBASE-20475?focusedCommentId=16467225=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16467225 > So prepared a patch for the revisiting.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18480) The cost of BaseLoadBalancer.cluster is changed even if the rollback is done
[ https://issues.apache.org/jira/browse/HBASE-18480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18480: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > The cost of BaseLoadBalancer.cluster is changed even if the rollback is done > > > Key: HBASE-18480 > URL: https://issues.apache.org/jira/browse/HBASE-18480 > Project: HBase > Issue Type: Bug > Components: Balancer >Affects Versions: 3.0.0, 1.3.0, 1.2.6, 2.0.0-alpha-1 >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Major > Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 2.0.0 > > Attachments: HBASE-18480.branch-1.2.v0.patch, > HBASE-18480.branch-1.3.v0.patch, HBASE-18480.branch-1.v0.patch, > HBASE-18480.branch-1.v1.patch, HBASE-18480.v0.patch, HBASE-18480.v1.patch, > HBASE-18480.v1.patch > > > If the cost of cluster isn't restored after the undo action, > StochasticLoadBalancer will be hard to generate the "good" action to balance > the cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19685) Fix TestFSErrorsExposed#testFullSystemBubblesFSErrors
[
https://issues.apache.org/jira/browse/HBASE-19685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19685:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix TestFSErrorsExposed#testFullSystemBubblesFSErrors
> -
>
> Key: HBASE-19685
> URL: https://issues.apache.org/jira/browse/HBASE-19685
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.3.2, 1.4.1, 1.5.0, 1.2.7, 2.0.0-beta-2, 2.0.0
>
> Attachments: HBASE-19685.v0.patch
>
>
> {code}
> java.lang.AssertionError
> at
> org.apache.hadoop.hbase.regionserver.TestFSErrorsExposed.testFullSystemBubblesFSErrors(TestFSErrorsExposed.java:221)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19056) TestCompactionInDeadRegionServer is top of the flakies charts!
[ https://issues.apache.org/jira/browse/HBASE-19056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19056: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TestCompactionInDeadRegionServer is top of the flakies charts! > --- > > Key: HBASE-19056 > URL: https://issues.apache.org/jira/browse/HBASE-19056 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: Ted Yu >Priority: Major > Fix For: 1.4.0, 2.0.0-beta-1, 2.0.0 > > Attachments: 19056.branch-1.patch, 19056.v5.txt, 19056.v6.txt, > 19056.v7.txt > > > The test came in recently as part of HBASE-17712 "Remove/Simplify the logic > of RegionScannerImpl.handleFileNotFound" > [~Apache9] when you have a chance, help me out. I was going to just remove > the test since it made no sense to me but then I saw you wrote it (smile). > When the region.compact(true); is called on the end, what is supposed to be > going on? > When I trace, the compact is not done because the Region is not writeEnabled > (we check if Region is writeEnabled down in Store before we go ahead and > compact). So, I thought the problem was that the region reference was stale > because it came from the rsToSuspend which had just been killed. > After a while, I figured that you intend the region reference to be stale so > you can try an append AFTER the WAL has been taken over by WAL splitter. > But the writeEnabled flag is set so compactions don't run. I tried unsetting > this flag and closed flags and but compaction won't run. > Was this your intent sir? If so, I'll work w/ it np. Just looking for > clarity. Thanks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18323:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Assignee: Shibin Zhang
>Priority: Minor
> Fix For: 1.4.0, 2.0.0
>
> Attachments: HBASE-18323-V2.patch, HBASE-18323-V3.patch,
> HBASE-18323-V4.patch, HBASE-18323-V5.patch, HBASE-18323.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18311) clean up the quickstart guide
[ https://issues.apache.org/jira/browse/HBASE-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18311: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > clean up the quickstart guide > - > > Key: HBASE-18311 > URL: https://issues.apache.org/jira/browse/HBASE-18311 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-18311.patch > > > extra commas, period, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18481) The autoFlush flag was not used in PE tool
[ https://issues.apache.org/jira/browse/HBASE-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18481: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > The autoFlush flag was not used in PE tool > -- > > Key: HBASE-18481 > URL: https://issues.apache.org/jira/browse/HBASE-18481 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12, 2.0.0 > > Attachments: HBASE-18481.patch > > > After HBASE-12728, PE used the BufferedMutator for random/sequential write > test and the autoFlush flag was not used. So all write test will buffered the > write request and send as a batch request when the buffer has filled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19037) BLOCKCACHE not work in console
[
https://issues.apache.org/jira/browse/HBASE-19037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19037:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> BLOCKCACHE not work in console
> --
>
> Key: HBASE-19037
> URL: https://issues.apache.org/jira/browse/HBASE-19037
> Project: HBase
> Issue Type: Bug
> Components: API
>Affects Versions: 1.2.6
>Reporter: Александр
>Priority: Major
>
> I'm testing the speed. At the time of the request, I know part of the key.
> ```
> scan 'id_bank',
> {STARTROW=>"24168557"+"\137",STOPROW=>"24168557"+"\177",COLUMNS => ['high',
> 'low'], BLOCKCACHE => 'true'}
> ```
> When I run the scan, the response returns a short time, and if I make a
> second request, the answer is already returned quickly, why?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20358) Fix bin/hbase thrift usage text
[
https://issues.apache.org/jira/browse/HBASE-20358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20358:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix bin/hbase thrift usage text
> ---
>
> Key: HBASE-20358
> URL: https://issues.apache.org/jira/browse/HBASE-20358
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0-beta-2
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-20358.branch-2.0.001.patch
>
>
> 1. Thrift server usage text does not say anything about it requires a
> {{start}} or {{stop}} argument.
> 2. It ignores {{stop}} argument, it acts as the same as for {{start}}.
> According to this comment:
> {code:java}
> // This is so complicated to please both bin/hbase and bin/hbase-daemon.
> // hbase-daemon provides "start" and "stop" arguments
> // hbase should print the help if no argument is provided
> {code}
> {{start}} and {{stop}} is just supported because {{bin/hbase-daemon}}, but
> hbase-daemon kills the process instead of calling it with a {{stop}} argument.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18890) Backport HBASE-14499 (Master coprocessors shutdown will not happen on master abort) to branch-1
[ https://issues.apache.org/jira/browse/HBASE-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18890: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Backport HBASE-14499 (Master coprocessors shutdown will not happen on master > abort) to branch-1 > --- > > Key: HBASE-18890 > URL: https://issues.apache.org/jira/browse/HBASE-18890 > 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: Major > Fix For: 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18890-branch-1.patch, HBASE-18890-branch-1.patch > > > Backport HBASE-14499 to branch-1 and other branches also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19941) Flaky TestCreateTableProcedure times out in nightly, needs to LargeTests
[ https://issues.apache.org/jira/browse/HBASE-19941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19941: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Flaky TestCreateTableProcedure times out in nightly, needs to LargeTests > > > Key: HBASE-19941 > URL: https://issues.apache.org/jira/browse/HBASE-19941 > Project: HBase > Issue Type: Bug > Components: test >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 > > Attachments: HBASE-19941.branch-2.001.patch > > > Currently its categorized as MediumTests but sometimes running all test in > this class take more than 180 seconds. Here is the comparison of runtimes > between local runs (on my dev machine) and in nightly runs: > ||Test||Local (seconds)||Nihgtly (seconds)|| > |testSimpleCreateWithSplits|~1.5|~12| > |testRollbackAndDoubleExecutionOnMobTable|~4.7|~21| > |testSimpleCreate|~1.7|~11| > |testRollbackAndDoubleExecution|~4.3|~18| > |testMRegions|~26.4|Timed out after 90 seconds| > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19329) hbase regionserver log output error (quota)
[ https://issues.apache.org/jira/browse/HBASE-19329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19329: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > hbase regionserver log output error (quota) > > > Key: HBASE-19329 > URL: https://issues.apache.org/jira/browse/HBASE-19329 > Project: HBase > Issue Type: Bug >Affects Versions: 1.3.1 >Reporter: gehaijiang >Priority: Major > > 2017-11-16 02:50:33,474 WARN > [blackstone064030,16020,1510632966258_ChoreService_1] quotas.QuotaCache: > Unable to read user from quota table > org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 3 > actions: Table 'hbase:quota' was not found, got: hbase:namespace.: 3 times, > servers with issues: null > , > at > org.apache.hadoop.hbase.quotas.QuotaTableUtil.doGet(QuotaTableUtil.java:330) > at > org.apache.hadoop.hbase.quotas.QuotaUtil.fetchUserQuotas(QuotaUtil.java:155) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore$3.fetchEntries(QuotaCache.java:256) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore.fetch(QuotaCache.java:290) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore.fetchUserQuotaState(QuotaCache.java:248) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore.chore(QuotaCache.java:213) > 2017-11-16 02:55:33,453 WARN > [blackstone064030,16020,1510632966258_ChoreService_1] quotas.QuotaCache: > Unable to read namespace from quota table > org.apache.hadoop.hbase.TableNotFoundException: Table 'hbase:quota' was not > found, got: hbase:namespace. > at > org.apache.hadoop.hbase.quotas.QuotaTableUtil.doGet(QuotaTableUtil.java:330) > at > org.apache.hadoop.hbase.quotas.QuotaUtil.fetchGlobalQuotas(QuotaUtil.java:220) > at > org.apache.hadoop.hbase.quotas.QuotaUtil.fetchNamespaceQuotas(QuotaUtil.java:207) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore$1.fetchEntries(QuotaCache.java:226) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore.fetch(QuotaCache.java:290) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore.fetchNamespaceQuotaState(QuotaCache.java:218) > at > org.apache.hadoop.hbase.quotas.QuotaCache$QuotaRefresherChore.chore(QuotaCache.java:211) > 2017-11-16 02:55:33,488 WARN > [blackstone064030,16020,1510632966258_ChoreService_1] quotas.QuotaCache: > Unable to read table from quota table > org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed > 47 actions: Table 'hbase:quota' was not found, got: hbase:namespace.: 47 > times, servers with issues: nu > ll, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20744) Address FindBugs warnings in branch-1
[
https://issues.apache.org/jira/browse/HBASE-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20744:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Address FindBugs warnings in branch-1
> -
>
> Key: HBASE-20744
> URL: https://issues.apache.org/jira/browse/HBASE-20744
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Xu Cang
>Priority: Major
> Fix For: 1.5.0
>
> Attachments: HBASE-20744.branch-1.001.patch,
> HBASE-20744.branch-1.002.patch
>
>
> From
> https://builds.apache.org/job/HBase%20Nightly/job/branch-1/350//JDK8_Nightly_Build_Report_(Hadoop2)/
> :
> {code}
> FindBugs module:hbase-common
> Inconsistent synchronization of
> org.apache.hadoop.hbase.io.encoding.EncodedDataBlock$BufferGrabbingByteArrayOutputStream.ourBytes;
> locked 50% of time Unsynchronized access at EncodedDataBlock.java:50% of
> time Unsynchronized access at EncodedDataBlock.java:[line 258]
> {code}
> {code}
> FindBugs module:hbase-hadoop2-compat
> java.util.concurrent.ScheduledThreadPoolExecutor stored into non-transient
> field MetricsExecutorImpl$ExecutorSingleton.scheduler At
> MetricsExecutorImpl.java:MetricsExecutorImpl$ExecutorSingleton.scheduler At
> MetricsExecutorImpl.java:[line 51]
> {code}
> {code}
> FindBugs module:hbase-server
> instanceof will always return false in
> org.apache.hadoop.hbase.quotas.RegionServerQuotaManager.checkQuota(Region,
> int, int, int), since a org.apache.hadoop.hbase.quotas.RpcThrottlingException
> can't be a org.apache.hadoop.hbase.quotas.ThrottlingException At
> RegionServerQuotaManager.java:in
> org.apache.hadoop.hbase.quotas.RegionServerQuotaManager.checkQuota(Region,
> int, int, int), since a org.apache.hadoop.hbase.quotas.RpcThrottlingException
> can't be a org.apache.hadoop.hbase.quotas.ThrottlingException At
> RegionServerQuotaManager.java:[line 193]
> instanceof will always return true for all non-null values in
> org.apache.hadoop.hbase.quotas.RegionServerQuotaManager.checkQuota(Region,
> int, int, int), since all
> org.apache.hadoop.hbase.quotas.RpcThrottlingException are instances of
> org.apache.hadoop.hbase.quotas.RpcThrottlingException At
> RegionServerQuotaManager.java:for all non-null values in
> org.apache.hadoop.hbase.quotas.RegionServerQuotaManager.checkQuota(Region,
> int, int, int), since all
> org.apache.hadoop.hbase.quotas.RpcThrottlingException are instances of
> org.apache.hadoop.hbase.quotas.RpcThrottlingException At
> RegionServerQuotaManager.java:[line 199]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19260) Add lock back to avoid parallel accessing meta to locate region
[
https://issues.apache.org/jira/browse/HBASE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19260:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Add lock back to avoid parallel accessing meta to locate region
> ---
>
> Key: HBASE-19260
> URL: https://issues.apache.org/jira/browse/HBASE-19260
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.1, 1.2.6, 2.0.0-alpha-3, 1.1.12
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Major
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19260.patch, HBASE-19260.v2.patch
>
>
> In branch-0.98 we have below codes to avoid accessing meta in parallel in
> {{HConnectionManager}}:
> {code}
> Result regionInfoRow;
> // This block guards against two threads trying to load the meta
> // region at the same time. The first will load the meta region and
> // the second will use the value that the first one found.
> if (useCache) {
> if (TableName.META_TABLE_NAME.equals(parentTable) && usePrefetch
> &&
> getRegionCachePrefetch(tableName)) {
> synchronized (regionLockObject) {
> // Check the cache again for a hit in case some other thread
> made the
> // same query while we were waiting on the lock.
> ...
> }
> }
> ...
> {code}
> while in HBASE-10018 we removed such logic along with
> region-location-prefetching.
> We regard this as an unexpected behavior change and observed below phenomenon
> in our product env:
> 1. Unnecessary connection setup to meta when multiple threads locating region
> in a client process
> 2. Priority handler of the RS holding meta region exhausted, application keep
> retrying and cause a vicious circle
> To resolve this problem, we propose to add the {{userRegionLock}} back and
> keep the behavior in accordance with 0.98
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19465) Required httpcore and httpclient jars not included in binary distribution
[
https://issues.apache.org/jira/browse/HBASE-19465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19465:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Required httpcore and httpclient jars not included in binary distribution
> -
>
> Key: HBASE-19465
> URL: https://issues.apache.org/jira/browse/HBASE-19465
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Blocker
> Fix For: 1.4.0
>
> Attachments: HBASE-19465-branch-1.patch
>
>
> The httpcore and httpclient dependency jars are not included into the binary
> distribution. This means MR/YARN jobs will fail if launched from the binary
> tarball as distributed, including those running in "local mode", e.g. ITBLL:
> {noformat}
> 2017-12-08 22:40:36,134 INFO [LocalJobRunner Map Task Executor #0]
> mapred.LocalJobRunner: Finishing task: attempt_local936234315_0001_m_03_0
> 2017-12-08 22:40:36,134 INFO [Thread-23] mapred.LocalJobRunner: map task
> executor complete.
> 2017-12-08 22:40:36,147 WARN [Thread-23] mapred.LocalJobRunner:
> job_local936234315_0001
> java.lang.NoClassDefFoundError: org/apache/http/client/methods/HttpUriRequest
> at
> org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:546)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.http.client.methods.HttpUriRequest
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 1 more
> Exception in thread "Thread-23" java.lang.NoClassDefFoundError:
> org/apache/http/client/methods/HttpUriRequest
> at
> org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:562)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.http.client.methods.HttpUriRequest
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 1 more
> 2017-12-08 22:40:37,078 INFO [main] mapreduce.Job: Job
> job_local936234315_0001 failed with state FAILED due to: NA
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19447) INFO level logging of GetClusterStatus from HMaster is too chatty
[ https://issues.apache.org/jira/browse/HBASE-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19447: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > INFO level logging of GetClusterStatus from HMaster is too chatty > - > > Key: HBASE-19447 > URL: https://issues.apache.org/jira/browse/HBASE-19447 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Major > Fix For: 1.4.0, 2.0.0 > > > Should be DEBUG. Should be wrapped with a logLevel check. > ./hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java:2409: > LOG.info(getClientIdAuditPrefix() + " get ClusterStatus, status=" + > status); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18759) Fix hbase-shaded-check-invariants failure
[
https://issues.apache.org/jira/browse/HBASE-18759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18759:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Fix hbase-shaded-check-invariants failure
> -
>
> Key: HBASE-18759
> URL: https://issues.apache.org/jira/browse/HBASE-18759
> Project: HBase
> Issue Type: Bug
> Components: Client, mapreduce
>Reporter: Appy
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0-alpha-3, 2.0.0
>
> Attachments: HBASE-18759.0.patch
>
>
> Here's the error.
> {noformat}
> [ERROR] Found artifact with unexpected contents:
> '/Users/appy/apache/hbase/hbase-shaded/hbase-shaded-server/target/hbase-shaded-server-3.0.0-SNAPSHOT.jar'
> Please check the following and either correct the build or update
> the allowed list with reasoning.
> about.html
> org/eclipse/
> org/eclipse/jetty/
> org/eclipse/jetty/http/
> org/eclipse/jetty/http/encoding.properties
> org/eclipse/jetty/http/GZIPContentDecoder$State.class
> org/eclipse/jetty/http/HttpFields$Itr.class
> org/eclipse/jetty/http/HttpParser$HttpHandler.class
> org/eclipse/jetty/http/HttpScheme.class
> org/eclipse/jetty/http/HttpURI.class
> org/eclipse/jetty/http/pathmap/
> org/eclipse/jetty/http/pathmap/PathMappings$1.class
> org/eclipse/jetty/http/pathmap/PathSpecGroup.class
> org/eclipse/jetty/http/pathmap/PathSpecSet$1.class
> org/eclipse/jetty/http/pathmap/RegexPathSpec.class
> org/eclipse/jetty/http/PathMap$MappedEntry.class
> org/eclipse/jetty/http/QuotedCSV$State.class
> org/eclipse/jetty/http/QuotedQualityCSV$1.class
> org/eclipse/jetty/http/DateParser.class
> org/eclipse/jetty/http/Http1FieldPreEncoder.class
> org/eclipse/jetty/http/HttpContent$ContentFactory.class
> org/eclipse/jetty/http/HttpFields$1.class
> org/eclipse/jetty/http/HttpFields.class
> org/eclipse/jetty/http/HttpStatus$Code.class
> org/eclipse/jetty/http/pathmap/UriTemplatePathSpec.class
> org/eclipse/jetty/http/ResourceHttpContent.class
> org/eclipse/jetty/http/BadMessageException.class
> org/eclipse/jetty/http/GZIPContentDecoder$1.class
> org/eclipse/jetty/http/HttpGenerator$Result.class
> org/eclipse/jetty/http/HttpParser$State.class
> org/eclipse/jetty/http/HttpURI$State.class
> org/eclipse/jetty/http/QuotedCSV.class
> org/eclipse/jetty/http/CompressedContentFormat.class
> org/eclipse/jetty/http/HttpField$LongValueHttpField.class
> org/eclipse/jetty/http/HttpGenerator$2.class
> org/eclipse/jetty/http/HttpMethod.class
> org/eclipse/jetty/http/HttpParser$ComplianceHandler.class
> org/eclipse/jetty/http/HttpParser$RequestHandler.class
> org/eclipse/jetty/http/HttpStatus.class
> org/eclipse/jetty/http/MetaData$Response.class
> org/eclipse/jetty/http/MimeTypes$Type.class
> org/eclipse/jetty/http/pathmap/PathMappings.class
> org/eclipse/jetty/http/PathMap$PathSet.class
> org/eclipse/jetty/http/QuotedQualityCSV.class
> org/eclipse/jetty/http/CookieCompliance.class
> org/eclipse/jetty/http/GZIPContentDecoder.class
> org/eclipse/jetty/http/HttpFields$2.class
> org/eclipse/jetty/http/HttpGenerator$State.class
> org/eclipse/jetty/http/HttpHeader.class
> org/eclipse/jetty/http/HttpParser$IllegalCharacterException.class
> org/eclipse/jetty/http/HttpTokens$EndOfContent.class
> org/eclipse/jetty/http/HttpURI$1.class
> org/eclipse/jetty/http/mime.properties
> org/eclipse/jetty/http/PreEncodedHttpField.class
> org/eclipse/jetty/http/DateGenerator$1.class
> org/eclipse/jetty/http/HostPortHttpField.class
> org/eclipse/jetty/http/HttpCompliance.class
> org/eclipse/jetty/http/HttpFieldPreEncoder.class
> org/eclipse/jetty/http/HttpGenerator$PreparedResponse.class
> org/eclipse/jetty/http/HttpParser$1.class
> org/eclipse/jetty/http/HttpParser$ResponseHandler.class
> org/eclipse/jetty/http/HttpTokens.class
> org/eclipse/jetty/http/HttpVersion.class
> org/eclipse/jetty/http/MetaData.class
> org/eclipse/jetty/http/pathmap/MappedResource.class
> org/eclipse/jetty/http/pathmap/PathSpec.class
> org/eclipse/jetty/http/pathmap/PathSpecSet.class
> org/eclipse/jetty/http/PreEncodedHttpField$1.class
> org/eclipse/jetty/http/QuotedCSV$1.class
> org/eclipse/jetty/http/Syntax.class
> org/eclipse/jetty/http/DateGenerator.class
> org/eclipse/jetty/http/HttpContent.class
> org/eclipse/jetty/http/HttpField$IntValueHttpField.class
> org/eclipse/jetty/http/HttpField.class
> org/eclipse/jetty/http/HttpGenerator.class
> org/eclipse/jetty/http/MetaData$Request.class
> org/eclipse/jetty/http/MimeTypes.class
>
[jira] [Issue Comment Deleted] (HBASE-20762) precommit should archive generated LICENSE file
[
https://issues.apache.org/jira/browse/HBASE-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20762:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> precommit should archive generated LICENSE file
> ---
>
> Key: HBASE-20762
> URL: https://issues.apache.org/jira/browse/HBASE-20762
> Project: HBase
> Issue Type: Bug
> Components: build, community
>Reporter: Mike Drob
>Priority: Major
>
> When a precommit run fails due to license issues, we get pointed to a file in
> our maven logs:
> {noformat}
> /testptch/hbase/hbase-assembly/target/maven-shared-archive-resources/META-INF/LICENSE
> {noformat}
> But we don't have that file saved, so we don't know what the actual failure
> was. So we should save that in our build artifacts. Or maybe we can print a
> snippet from that file directly into the maven log. Both would be acceptable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20678) NPE in ReplicationSourceManager#NodeFailoverWorker
[
https://issues.apache.org/jira/browse/HBASE-20678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20678:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> NPE in ReplicationSourceManager#NodeFailoverWorker
> --
>
> Key: HBASE-20678
> URL: https://issues.apache.org/jira/browse/HBASE-20678
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Fix For: 2.1.0
>
> Attachments: HBASE-20678.master.001.patch,
> HBASE-20678.master.002.patch, HBASE-20678.master.003.patch
>
>
> 2018-06-04 10:28:43,362 INFO [ReplicationExecutor-0]
> replication.ZKReplicationQueueStorage(432): Claim queue queueId=1 from
> hao-optiplex-7050,38491,1528079278158 to
> hao-optiplex-7050,39931,1528079278272 failed with
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode =
> NoNode, someone else took the log?
> Exception in thread "ReplicationExecutor-0" java.lang.NullPointerException
>
>
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager$NodeFailoverWorker.run(ReplicationSourceManager.java:858)
> 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)
> ZKReplicationQueueStorage's claimQueue method may return null when got
> NoNodeException.
> {code:java}
> Pair> peer =
> queueStorage.claimQueue(deadRS,
> queues.get(ThreadLocalRandom.current().nextInt(queues.size())),
> server.getServerName());
> long sleep = sleepBeforeFailover / 2;
> if (!peer.getSecond().isEmpty()) {
> newQueues.put(peer.getFirst(), peer.getSecond());
> sleep = sleepBeforeFailover;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20369) Document incompatibilities between HBase 1.x and HBase 2.0
[ https://issues.apache.org/jira/browse/HBASE-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20369: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Document incompatibilities between HBase 1.x and HBase 2.0 > -- > > Key: HBASE-20369 > URL: https://issues.apache.org/jira/browse/HBASE-20369 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Thiriguna Bharat Rao >Assignee: Thiriguna Bharat Rao >Priority: Critical > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20369.patch, HBASE-20369_v1.patch, > HBASE-20369_v2.patch, HBASE-20369_v3.patch, HBASE-20369_v4.patch, > HBASE-20369_v5.patch, HBASE-20369_v6.patch, HBASE-20369_v7.patch, > HBASE-20369_v8.patch, HBASE-20369_v9.patch, HBase-20369_v10.patch, book.adoc > > > Hi, > I compiled a draft document for the HBase incompatibilities from the raw > source content that was available in HBase Beta 1 site. Can someone please > review and provide a feedback or share your comments on this document? > Appreciate your support and time. > > Best Regards, > Triguna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20866) HBase 1.x scan performance degradation compared to 0.98 version
[
https://issues.apache.org/jira/browse/HBASE-20866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20866:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> HBase 1.x scan performance degradation compared to 0.98 version
> ---
>
> Key: HBASE-20866
> URL: https://issues.apache.org/jira/browse/HBASE-20866
> Project: HBase
> Issue Type: Bug
> Components: Performance
>Affects Versions: 1.3.2
>Reporter: Vikas Vishwakarma
>Assignee: Vikas Vishwakarma
>Priority: Critical
> Fix For: 1.3.3
>
> Attachments: HBASE-20866.branch-1.3.001.patch,
> HBASE-20866.branch-1.3.002.patch, HBASE-20866.branch-1.3.003.patch
>
>
> Internally while testing 1.3 as part of migration from 0.98 to 1.3 we
> observed perf degradation in scan performance for phoenix queries varying
> from few 10's to upto 200% depending on the query being executed. We tried
> simple native HBase scan and there also we saw upto 40% degradation in
> performance when the number of column qualifiers are high (40-50+)
> To identify the root cause of performance diff between 0.98 and 1.3 we
> carried out lot of experiments with profiling and git bisect iterations,
> however we were not able to identify any particular source of scan
> performance degradation and it looked like this is an accumulated degradation
> of 5-10% over various enhancements and refactoring.
> We identified few major enhancements like partialResult handling,
> ScannerContext with heartbeat processing, time/size limiting, RPC
> refactoring, etc that could have contributed to small degradation in
> performance which put together could be leading to large overall degradation.
> One of the changes is
> [HBASE-11544|https://jira.apache.org/jira/browse/HBASE-11544] which
> implements partialResult handling. In ClientScanner.java the results received
> from server are cached on the client side by converting the result array into
> an ArrayList. This function gets called in a loop depending on the number of
> rows in the scan result. Example for ten’s of millions of rows scanned, this
> can be called in the order of millions of times.
> In almost all the cases 99% of the time (except for handling partial results,
> etc). We are just taking the resultsFromServer converting it into a ArrayList
> resultsToAddToCache in addResultsToList(..) and then iterating over the list
> again and adding it to cache in loadCache(..) as given in the code path below
> In ClientScanner → loadCache(..) → getResultsToAddToCache(..) →
> addResultsToList(..) →
> {code:java}
> loadCache() {
> ...
> List resultsToAddToCache =
> getResultsToAddToCache(values, callable.isHeartbeatMessage());
> ...
> …
> for (Result rs : resultsToAddToCache) {
> rs = filterLoadedCell(rs);
> cache.add(rs);
> ...
> }
> }
> getResultsToAddToCache(..) {
> ..
> final boolean isBatchSet = scan != null && scan.getBatch() > 0;
> final boolean allowPartials = scan != null &&
> scan.getAllowPartialResults();
> ..
> if (allowPartials || isBatchSet) {
> addResultsToList(resultsToAddToCache, resultsFromServer, 0,
> (null == resultsFromServer ? 0 : resultsFromServer.length));
> return resultsToAddToCache;
> }
> ...
> }
> private void addResultsToList(List outputList, Result[] inputArray,
> int start, int end) {
> if (inputArray == null || start < 0 || end > inputArray.length) return;
> for (int i = start; i < end; i++) {
> outputList.add(inputArray[i]);
> }
> }{code}
>
> It looks like we can avoid the result array to arraylist conversion
> (resultsFromServer --> resultsToAddToCache ) for the first case which is also
> the most frequent case and instead directly take the values arraay returned
> by callable and add it to the cache without converting it into ArrayList.
> I have taken both these flags allowPartials and isBatchSet out in loadcahe()
> and I am directly adding values to scanner cache if the above condition is
> pass instead of coverting it into arrayList by calling
> getResultsToAddToCache(). For example:
> {code:java}
> protected void loadCache() throws IOException {
> Result[] values = null;
> ..
> final boolean isBatchSet = scan != null && scan.getBatch() > 0;
> final boolean allowPartials = scan != null && scan.getAllowPartialResults();
> ..
> for (;;) {
> try {
> values = call(callable, caller, scannerTimeout);
> ..
> } catch (DoNotRetryIOException | NeedUnmanagedConnectionException e) {
> ..
> }
> if (allowPartials || isBatchSet) { // DIRECTLY COPY values TO CACHE
> if (values != null) {
> for (int v=0; v Result rs = values[v];
>
> cache.add(rs);
> ...
> } else { // DO ALL THE REGULAR PARTIAL RESULT HANDLING ..
> List
[jira] [Issue Comment Deleted] (HBASE-19223) Remove references to Date Tiered compaction from branch-1.2 and branch-1.1 ref guide
[ https://issues.apache.org/jira/browse/HBASE-19223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19223: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Remove references to Date Tiered compaction from branch-1.2 and branch-1.1 > ref guide > > > Key: HBASE-19223 > URL: https://issues.apache.org/jira/browse/HBASE-19223 > Project: HBase > Issue Type: Bug > Components: Compaction, documentation >Affects Versions: 1.1.5, 1.2.2 >Reporter: chilianyi >Assignee: Sean Busbey >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-1, 1.1.13, 2.0.0 > > Attachments: HBASE-19223-branch-1.2.v0.patch, > HBASE-19223-branch-1.2.v1.patch > > > I have download hbase 1.2.6 src package. But not found class > DateTieredStoreEngine, which is present in document: > https://hbase.apache.org/1.2/book.html. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19021) Restore a few important missing logics for balancer in 2.0
[
https://issues.apache.org/jira/browse/HBASE-19021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-19021:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
> Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Fix For: 2.0.0-alpha-4, 2.0.0
>
> Attachments: HBASE-19021-master-v2.patch, HBASE-19021-master.patch,
> HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'.
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a
> {{testRebalanceOnRegionServerNumberChange}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18287) Remove log warning in PartitionedMobCompactor.java#getFileStatus
[ https://issues.apache.org/jira/browse/HBASE-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18287: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Remove log warning in PartitionedMobCompactor.java#getFileStatus > - > > Key: HBASE-18287 > URL: https://issues.apache.org/jira/browse/HBASE-18287 > Project: HBase > Issue Type: Bug > Components: mob >Affects Versions: 2.0.0-alpha-1 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Minor > Fix For: 2.0.0-alpha-3, 2.0.0 > > Attachments: HBASE-18287.master.001.patch, > HBASE-18287.master.002.patch > > > It is confusing as the FileNotFound is expected here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18771) Incorrect StoreFileRefresh leading to split and compaction failures
[ https://issues.apache.org/jira/browse/HBASE-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18771: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Incorrect StoreFileRefresh leading to split and compaction failures > --- > > Key: HBASE-18771 > URL: https://issues.apache.org/jira/browse/HBASE-18771 > Project: HBase > Issue Type: Bug >Affects Versions: 1.3.1 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Blocker > Fix For: 1.4.0, 1.3.2, 2.0.0 > > Attachments: HBASE-18771.branch-1.3.001.patch, > HBASE-18771.branch-1.3.002.patch, HBASE-18771.branch-1.3.003.patch, > HBASE-18771.branch-1.3.004.patch, HBASE-18771.branch-1.3.005.patch, > HBASE-18771.master.001.patch, HBASE-18771.master.002.patch, > HBASE-18771.master.003.patch > > > We ran into issues of compaction and split failures with 1.3 similar to > HBASE-18186 and HBASE-17406. Here's what i believe is happening - > Lets say we have 4 store files that are compacted to form a new one. At this > point we now have 5 store files, however only 1(the newly formed) is open now > for the store and rest are waiting to get archived by HFileArchiver > Now before the files are archived we get a FNFE in a scanner. This results in > HRegion.RegionScannerImpl.handleFileNotFound(FileNotFoundException fnfe) > being called which results in region.refreshStoreFiles(true) -> > HStore.refreshStoreFiles() > HStore.refreshStoreFiles now checks the hdfs dir and adds the previously > compacted files back to the store, however these files are also present in > StoreFileManager's compactedFiles list. Now at this point HFileArchiver runs, > checks compactedFiles list and moves these files into the archive directory. > Now when compaction runs it gets: > 2017-09-04 12:30:13,899 ERROR [ctions-1504505399609] > regionserver.CompactSplitThread - Compaction selection failed regionName = > , storeName = 0, priority = 26, time = 1504528213899 > java.io.FileNotFoundException: File does not exist: hdfs:// > at > org.apache.hadoop.hdfs.DistributedFileSystem$23.doCall(DistributedFileSystem.java:1337) > at > org.apache.hadoop.hdfs.DistributedFileSystem$23.doCall(DistributedFileSystem.java:1329) > at > org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) > at > org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1329) > at > org.apache.hadoop.fs.FilterFileSystem.getFileStatus(FilterFileSystem.java:422) > at > org.apache.hadoop.hbase.regionserver.StoreFileInfo.getReferencedFileStatus(StoreFileInfo.java:342) > at > org.apache.hadoop.hbase.regionserver.StoreFileInfo.getFileStatus(StoreFileInfo.java:355) > at > org.apache.hadoop.hbase.regionserver.StoreFileInfo.getModificationTime(StoreFileInfo.java:360) > at > org.apache.hadoop.hbase.regionserver.StoreFile.getModificationTimeStamp(StoreFile.java:325) > at > org.apache.hadoop.hbase.regionserver.StoreUtils.getLowestTimestamp(StoreUtils.java:63) > at > org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy.shouldPerformMajorCompaction(RatioBasedCompactionPolicy.java:65) > at > org.apache.hadoop.hbase.regionserver.compactions.SortedCompactionPolicy.selectCompaction(SortedCompactionPolicy.java:82) > at > org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.select(DefaultStoreEngine.java:107) > at > org.apache.hadoop.hbase.regionserver.HStore.requestCompaction(HStore.java:1679) > Similarly if a split happens after archival we fail after PONR while opening > daughter regions due to FNFE. This results in parent offline and daughters > also in a limbo since they're unable to open. Since we get the error after > PONR we also end up aborting the RS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20612) TestReplicationKillSlaveRSWithSeparateOldWALs sometimes fail because it uses an expired cluster conn
[
https://issues.apache.org/jira/browse/HBASE-20612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20612:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> TestReplicationKillSlaveRSWithSeparateOldWALs sometimes fail because it uses
> an expired cluster conn
>
>
> Key: HBASE-20612
> URL: https://issues.apache.org/jira/browse/HBASE-20612
> Project: HBase
> Issue Type: Bug
>Reporter: Zheng Hu
>Assignee: Zheng Hu
>Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20612.v1.patch, HBASE-20612.v2.patch,
> org.apache.hadoop.hbase.replication.TestReplicationKillSlaveRSWithSeparateOldWALs-output.txt
>
>
> {code}
> 2018-05-22 06:40:00,614 INFO [Thread-961] regionserver.HRegionServer(2144):
> * STOPPING region server 'asf911.gq1.ygridcore.net,42867,1526971178277'
> *
> 2018-05-22 06:40:00,614 INFO [Thread-961] regionserver.HRegionServer(2158):
> STOPPED: Stopping as part of the test
>
> 2018-05-22 06:41:01,018 DEBUG [Time-limited test]
> client.ResultBoundedCompletionService(226): Replica 0 returns
> java.net.SocketTimeoutException: callTimeout=6, callDuration=60515: Call
> to asf911.gq1.ygridcore.net/67.195.81.155:42867 failed on local exception:
> org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=34, waitTime=59332,
> rpcTimeout=59322 row 'eee' on table 'test' at
> region=test,eee,1526971188643.5aab2dd2e1d02b4e40be6d00422acd21.,
> hostname=asf911.gq1.ygridcore.net,42867,1526971178277, seqNum=2
> java.net.SocketTimeoutException: callTimeout=6, callDuration=60515: Call
> to asf911.gq1.ygridcore.net/67.195.81.155:42867 failed on local exception:
> org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=34, waitTime=59332,
> rpcTimeout=59322 row 'eee' on table 'test' at
> region=test,eee,1526971188643.5aab2dd2e1d02b4e40be6d00422acd21.,
> hostname=asf911.gq1.ygridcore.net,42867,1526971178277, seqNum=2
> at
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159)
> at
> org.apache.hadoop.hbase.client.ResultBoundedCompletionService$QueueingFuture.run(ResultBoundedCompletionService.java:80)
> 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)
> Caused by: java.io.IOException: Call to
> asf911.gq1.ygridcore.net/67.195.81.155:42867 failed on local exception:
> org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=34, waitTime=59332,
> rpcTimeout=59322
> at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:180)
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390)
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95)
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410)
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406)
> at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96)
> at
> org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199)
> at
> org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:663)
> at
> org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:738)
> at
> org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:466)
> ... 1 more
> Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=34,
> waitTime=59332, rpcTimeout=59322
> at
> org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20789) TestBucketCache#testCacheBlockNextBlockMetadataMissing is flaky
[ https://issues.apache.org/jira/browse/HBASE-20789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20789: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > TestBucketCache#testCacheBlockNextBlockMetadataMissing is flaky > --- > > Key: HBASE-20789 > URL: https://issues.apache.org/jira/browse/HBASE-20789 > Project: HBase > Issue Type: Bug >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0, 1.5.0, 1.4.6, 2.0.2 > > Attachments: > 0001-HBASE-20789-TestBucketCache-testCacheBlockNextBlockM.patch, > HBASE-20789.branch-1.v1.patch, HBASE-20789.v1.patch, HBASE-20789.v2.patch, > HBASE-20789.v3.patch, HBASE-20789.v4.patch, HBASE-20789.v5.patch, > bucket-33718.out > > > The UT failed frequently in our internal branch-2... Will dig into the UT. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20664) Variable shared across multiple threads
[ https://issues.apache.org/jira/browse/HBASE-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20664: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Variable shared across multiple threads > --- > > Key: HBASE-20664 > URL: https://issues.apache.org/jira/browse/HBASE-20664 > Project: HBase > Issue Type: Bug >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Major > Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 1.4.5, 1.2.6.1, > 1.3.2.1, 2.0.0.1 > > > Some static analysis found a variable which was used across multiple threads > without any synchronization that would allow race conditions. > The variable does not need to be a member of the class, instead just made a > local variable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20855) PeerConfigTracker only supporting one listener will cause problem when there is a recovered replication queue
[
https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-20855:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> PeerConfigTracker only supporting one listener will cause problem when there
> is a recovered replication queue
> -
>
> Key: HBASE-20855
> URL: https://issues.apache.org/jira/browse/HBASE-20855
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.4.0, 1.5.0
>Reporter: Jingyun Tian
>Assignee: Jingyun Tian
>Priority: Major
> Fix For: 1.5.0, 1.4.6
>
> Attachments: HBASE-20855.branch-1.001.patch,
> HBASE-20855.branch-1.002.patch, HBASE-20855.branch-1.003.patch,
> HBASE-20855.branch-1.004.patch, HBASE-20855.branch-1.005.patch,
> HBASE-20855.branch-1.006.patch, HBASE-20855.branch-1.007.patch
>
>
> {code}
> public void init(Context context) throws IOException {
> this.ctx = context;
> if (this.ctx != null){
> ReplicationPeer peer = this.ctx.getReplicationPeer();
> if (peer != null){
> peer.trackPeerConfigChanges(this);
> } else {
> LOG.warn("Not tracking replication peer config changes for Peer Id " +
> this.ctx.getPeerId() +
> " because there's no such peer");
> }
> }
> }
> {code}
> As we know, replication source will set itself to the PeerConfigTracker in
> ReplicationPeer. When there is one or more recovered queue, each queue will
> generate a new replication source, But they share the same ReplicationPeer.
> Then when it calls setListener, the new generated one will cover the older
> one. Thus there will only has one ReplicationPeer that receive the peer
> config change notify.
> {code}
> public synchronized void setListener(ReplicationPeerConfigListener listener){
> this.listener = listener;
> }
> {code}
>
> To solve this, PeerConfigTracker need to support multiple listener and
> listener should be removed when the replication endpoint terminated.
> I will upload a patch later with fix and UT.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20017) BufferedMutatorImpl submit the same mutation repeatedly
[ https://issues.apache.org/jira/browse/HBASE-20017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-20017: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > BufferedMutatorImpl submit the same mutation repeatedly > --- > > Key: HBASE-20017 > URL: https://issues.apache.org/jira/browse/HBASE-20017 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0, 1.4.1, 1.4.2 >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Blocker > Fix For: 1.5.0, 1.4.2, 2.0.0 > > Attachments: HBASE-20017.branch-1.4.v0.patch.patch, > HBASE-20017.branch-1.v0.patch.patch, HBASE-20017.v0.patch.patch > > > BMI pass a iter of inner buffer to AsyncProcess to take the undealt > mutations, AsyncProcess call iter#next to get the mutation and then call > iter#remove to delete the mutation from inner buffer. Hence, There's a good > chance that the mutation is processed repeatedly in case there are a bunch > of threads which are running the flush. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-19712) Fix TestSnapshotQuotaObserverChore#testSnapshotSize
[ https://issues.apache.org/jira/browse/HBASE-19712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-19712: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Fix TestSnapshotQuotaObserverChore#testSnapshotSize > --- > > Key: HBASE-19712 > URL: https://issues.apache.org/jira/browse/HBASE-19712 > Project: HBase > Issue Type: Bug > Components: test >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Major > Fix For: 2.0.0-beta-1, 2.0.0 > > Attachments: HBASE-19712.v0.patch, HBASE-19712.v1.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18005) read replica: handle the case that region server hosting both primary replica and meta region is down
[ https://issues.apache.org/jira/browse/HBASE-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18005: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > read replica: handle the case that region server hosting both primary replica > and meta region is down > - > > Key: HBASE-18005 > URL: https://issues.apache.org/jira/browse/HBASE-18005 > Project: HBase > Issue Type: Bug >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Major > Fix For: 1.4.0, 2.0.0 > > Attachments: HBASE-18005-branch-1-v001.patch, > HBASE-18005-master-001.patch, HBASE-18005-master-002.patch, > HBASE-18005-master-003.patch, HBASE-18005-master-004.patch, > HBASE-18005-master-005.patch, HBASE-18005-master-006.patch > > > Identified one corner case in testing that when the region server hosting > both primary replica and the meta region is down, the client tries to reload > the primary replica location from meta table, it is supposed to clean up only > the cached location for specific replicaId, but it clears caches for all > replicas. Please see > https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionImplementation.java#L813 > Since it takes some time for regions to be reassigned (including meta > region), the following may throw exception > https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerWithReadReplicas.java#L173 > This exception needs to be caught and it needs to get cached location (in > this case, the primary replica's location is not available). If there are > cached locations for other replicas, it can still go ahead to get stale > values from secondary replicas. > With meta replica, it still helps to not clean up the caches for all replicas > as the info from primary meta replica is up-to-date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18049) It is not necessary to re-open the region when MOB files cannot be found
[
https://issues.apache.org/jira/browse/HBASE-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-18049:
--
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> It is not necessary to re-open the region when MOB files cannot be found
>
>
> Key: HBASE-18049
> URL: https://issues.apache.org/jira/browse/HBASE-18049
> Project: HBase
> Issue Type: Bug
> Components: Scanners
>Reporter: Jingcheng Du
>Assignee: Jingcheng Du
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-18049-V2.patch, HBASE-18049-V3.patch,
> HBASE-18049.patch
>
>
> In HBASE-17712, we try to re-open the region when store files cannot be
> found. This is useful for store files in a region, but is not necessary when
> the MOB files cannot be found, because the store files in a region only
> contain the references to the MOB files and a re-open of a region doesn't
> help the lost MOB files.
> In this JIRA, we will directly throw DNRIOE only when the MOB files are not
> found in {{MobStoreScanner}} and {{ReversedMobStoreScanner}}. Other logics
> keep the same.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-18321) [hbase-thirdparty] Fix generation of META-INF/DEPENDENCIES to include dependency list and versions
[ https://issues.apache.org/jira/browse/HBASE-18321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated HBASE-18321: -- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > [hbase-thirdparty] Fix generation of META-INF/DEPENDENCIES to include > dependency list and versions > -- > > Key: HBASE-18321 > URL: https://issues.apache.org/jira/browse/HBASE-18321 > Project: HBase > Issue Type: Bug > Components: hbase-thirdparty >Reporter: stack >Assignee: stack >Priority: Major > Fix For: thirdparty-1.0.1 > > Attachments: 18321.txt > > > Fix META-INF/DEPENDENCIES so it includes list of dependencies up in > hbase-thirdparty (Comment by [~zjushch]) on the vote for 1.0.0 of > hbase-thirdparty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
