[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Status: Patch Available (was: Open)
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v1.txt
First attempt at fixing the test: in case VisibilityController is not yet
initialized, retry writing new lables after a short wait.
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: (was: 11878-v1.txt)
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v1.txt
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v2.txt
Patch v2 adds VisibilityControllerNotReadyException which is used to detect
whether retry is needed.
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt, 11878-v2.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v2.txt
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt, 11878-v2.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: (was: 11878-v2.txt)
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt, 11878-v2.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v2.txt
Updated patch removing the whitespace.
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v3.txt
Patch v3 moves VisibilityControllerNotReadyException to hbase-client module.
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Fix Version/s: 0.98.6
2.0.0
0.99.0
Hadoop Flags: Reviewed
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.99.0, 2.0.0, 0.98.6
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v4.txt
Patch v4 addresses Andrew's comment.
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.99.0, 2.0.0, 0.98.6
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt,
11878-v4.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: (was: 11878-v4.txt)
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.99.0, 2.0.0, 0.98.6
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt,
11878-v4.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v4.txt
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.99.0, 2.0.0, 0.98.6
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt,
11878-v4.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Issue Type: Bug (was: Test)
Release Note:
A new exception, VisibilityControllerNotReadyException, is introduced for the
case where VisibilityController is being initialized. Client can respond to
this exception by retrying prior operation.
VisibilityControllerNotReadyException isn't a DoNotRetryIOException.
Updated release notes.
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.99.0, 2.0.0, 0.98.6
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt,
11878-v4.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Attachment: 11878-v5.txt
Patch v5 removes extra exclamation mark.
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.99.0, 2.0.0, 0.98.6
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt,
11878-v4.txt, 11878-v5.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11878) TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart sometimes fails due to VisibilityController not yet initialized
[
https://issues.apache.org/jira/browse/HBASE-11878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11878:
---
Status: Open (was: Patch Available)
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes fails due to VisibilityController not yet initialized
---
Key: HBASE-11878
URL: https://issues.apache.org/jira/browse/HBASE-11878
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.99.0, 2.0.0, 0.98.6
Attachments: 11878-v1.txt, 11878-v2.txt, 11878-v2.txt, 11878-v3.txt,
11878-v4.txt, 11878-v5.txt
In the thread w.r.t. first RC of 0.98.6,
http://search-hadoop.com/m/DHED4p2rw81 , Jean-Marc reported that
TestVisibilityLabelsWithDistributedLogReplay#testAddVisibilityLabelsOnRSRestart
sometimes failed on his machines.
From
http://server.distparser.com:81/hbase/with_teds_patch2/hbasetest1/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
:
{code}
result {
exception {
name: org.apache.hadoop.hbase.coprocessor.CoprocessorException
value: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
VisibilityController not yet initialized\n\tat
org.apache.hadoop.hbase.security.visibility.VisibilityController.addLabels(VisibilityController.java:638)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService$1.addLabels(VisibilityLabelsProtos.java:5014)\n\tat
org.apache.hadoop.hbase.protobuf.generated.VisibilityLabelsProtos$VisibilityLabelsService.callMethod(VisibilityLabelsProtos.java:5178)\n\tat
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5794)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1608)\n\tat
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1590)\n\tat
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30088)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2014)\n\tat
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)\n\tat
java.lang.Thread.run(Thread.java:744)\n
}
}
{code}
The above exception revealed a race condition: writing of labels ABC and
XYZ took place when VisibilityController was not yet initialized.
The test writes the labels only once, leading to assertion failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
