accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Coleman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4836) Tables do not always wait for online or offline
Date Fri, 02 Mar 2018 03:14:00 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383086#comment-16383086
] 

Ed Coleman commented on ACCUMULO-4836:
--------------------------------------

I am unclear on the proposed fix - actually I'm unclear on the problem - not saying this is
incorrect, I just don't understand the logic being proposed.

If the table is online - what is there to wait for? Should it not be that if the expected
state is not online, then check wait...

if(expectedState == TableStae.ONLINE){

  return;

}

if(wait){

  waitForTableStateTransisition(tableId, TableState.ONLINE);

  return;

}

> Tables do not always wait for online or offline
> -----------------------------------------------
>
>                 Key: ACCUMULO-4836
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4836
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.7.3
>            Reporter: Keith Turner
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.4, 1.9.0, 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> While investigating why TabletStateChangeIteratorIT it was discovered that online table
with wait=true does not always wait.  The test relied on this API to wait and that is why
it was failing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message