[jira] [Created] (HBASE-20083) Fix findbugs error for ReplicationSyncUp
Duo Zhang created HBASE-20083: - Summary: Fix findbugs error for ReplicationSyncUp Key: HBASE-20083 URL: https://issues.apache.org/jira/browse/HBASE-20083 Project: HBase Issue Type: Sub-task Reporter: Duo Zhang The static 'conf' field seems dodgy, I think it is OK to just remove it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20082) Fix findbugs errors only on master which introduced by HBASE-19397
Duo Zhang created HBASE-20082: - Summary: Fix findbugs errors only on master which introduced by HBASE-19397 Key: HBASE-20082 URL: https://issues.apache.org/jira/browse/HBASE-20082 Project: HBase Issue Type: Sub-task Components: findbugs Reporter: Duo Zhang Assignee: Duo Zhang Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20081) TestDisableTableProcedure sometimes hung in MiniHBaseCluster#waitUntilShutDown
Ted Yu created HBASE-20081:
--
Summary: TestDisableTableProcedure sometimes hung in
MiniHBaseCluster#waitUntilShutDown
Key: HBASE-20081
URL: https://issues.apache.org/jira/browse/HBASE-20081
Project: HBase
Issue Type: Test
Reporter: Ted Yu
https://builds.apache.org/job/HBase-2.0-hadoop3-tests/lastCompletedBuild/org.apache.hbase$hbase-server/testReport/org.apache.hadoop.hbase.master.procedure/TestDisableTableProcedure/org_apache_hadoop_hbase_master_procedure_TestDisableTableProcedure/
was one recent occurrence.
I noticed two things in test output:
{code}
2018-02-25 18:12:45,053 WARN [Time-limited test-EventThread]
master.RegionServerTracker(136): asf912.gq1.ygridcore.net,45649,1519582305777
is not online or isn't known to the master.The latter could be caused by a DNS
misconfiguration.
{code}
Since DNS misconfiguration was very unlikely on Apache Jenkins nodes, the above
should not have been logged.
{code}
2018-02-25 18:16:51,531 WARN [master/asf912:0.Chore.1]
master.CatalogJanitor(127): Failed scan of catalog table
java.io.IOException: connection is closed
at
org.apache.hadoop.hbase.MetaTableAccessor.getMetaHTable(MetaTableAccessor.java:263)
at
org.apache.hadoop.hbase.MetaTableAccessor.scanMeta(MetaTableAccessor.java:761)
at
org.apache.hadoop.hbase.MetaTableAccessor.scanMeta(MetaTableAccessor.java:680)
at
org.apache.hadoop.hbase.MetaTableAccessor.scanMetaForTableRegions(MetaTableAccessor.java:675)
at
org.apache.hadoop.hbase.master.CatalogJanitor.getMergedRegionsAndSplitParents(CatalogJanitor.java:188)
at
org.apache.hadoop.hbase.master.CatalogJanitor.getMergedRegionsAndSplitParents(CatalogJanitor.java:140)
at
org.apache.hadoop.hbase.master.CatalogJanitor.scan(CatalogJanitor.java:246)
at
org.apache.hadoop.hbase.master.CatalogJanitor.chore(CatalogJanitor.java:119)
at org.apache.hadoop.hbase.ScheduledChore.run(ScheduledChore.java:186)
{code}
The above was possibly related to the lost region server.
I searched test output of successful run where none of the above two can be
seen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20080) Have HBase shell warn users when cell visibility and simple authentication are in use together
Mike Thomsen created HBASE-20080:
Summary: Have HBase shell warn users when cell visibility and
simple authentication are in use together
Key: HBASE-20080
URL: https://issues.apache.org/jira/browse/HBASE-20080
Project: HBase
Issue Type: Improvement
Reporter: Mike Thomsen
When simple authentication and cell visibility are enabled, it's pretty easy
for users (particularly new ones) to accidentally log in as the same user that
is running HBase. That can lead to it looking like cell visibility isn't
working when it really is.
This is probably an issue mainly for local installations on development
machines, but it should show a warning saying something like "HBase is running
as \{principle} and you logged in as \{principle}. Cell visibility is enabled,
but will return all rows because you are acting as the superuser."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20079) Report all the new test classes missing HBaseClassTestRule in one patch
Ted Yu created HBASE-20079: -- Summary: Report all the new test classes missing HBaseClassTestRule in one patch Key: HBASE-20079 URL: https://issues.apache.org/jira/browse/HBASE-20079 Project: HBase Issue Type: Test Reporter: Ted Yu Currently if there are both new small and large tests without HBaseClassTestRule in a single patch, the QA bot would report the small test class as missing HBaseClassTestRule but not the large test. All new test classes missing HBaseClassTestRule should be reported in the same QA run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Still Failing: HBase Generate Website
Build status: Still Failing
The HBase website has not been updated to incorporate HBase commit
${CURRENT_HBASE_COMMIT}.
See https://builds.apache.org/job/hbase_generate_website/1265/console
