You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2015/04/24 18:26:38 UTC
[jira] [Commented] (ACCUMULO-3748) MultiInstanceReplicationIT
failed due to offline replication table
[ https://issues.apache.org/jira/browse/ACCUMULO-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511301#comment-14511301 ]
Christopher Tubbs commented on ACCUMULO-3748:
---------------------------------------------
This is probably due to the table status using ZooCache, and the typical zookeeper propagation delay.
> MultiInstanceReplicationIT failed due to offline replication table
> ------------------------------------------------------------------
>
> Key: ACCUMULO-3748
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3748
> Project: Accumulo
> Issue Type: Bug
> Components: test
> Reporter: Josh Elser
> Priority: Minor
> Fix For: 1.8.0, 1.7.1
>
>
> Saw this on a run:
> {noformat}
> Error Message
> org.apache.accumulo.core.client.TableOfflineException: Table accumulo.replication (+rep) is offline
> Stacktrace
> org.apache.accumulo.core.replication.ReplicationTableOfflineException: org.apache.accumulo.core.client.TableOfflineException: Table accumulo.replication (+rep) is offline
> at org.apache.accumulo.core.client.impl.ConnectorImpl.getTableId(ConnectorImpl.java:83)
> at org.apache.accumulo.core.client.impl.ConnectorImpl.createScanner(ConnectorImpl.java:152)
> at org.apache.accumulo.core.replication.ReplicationTable.getScanner(ReplicationTable.java:61)
> at org.apache.accumulo.test.replication.MultiInstanceReplicationIT.dataReplicatedToCorrectTableWithoutDrain(MultiInstanceReplicationIT.java:647)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)