accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3618) Tests which invoke `accumulo admin stop ...` fail
Date Tue, 24 Feb 2015 19:17:04 GMT

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

Josh Elser commented on ACCUMULO-3618:
--------------------------------------

I would agree with your assessment. At this point, I'm open the opinion that the change to
TabletStateChangeIterator was rather untested and should be backed out of 1.5 and 1.6 entirely.

Making the changes you outlined in 1.7 seems reasonable.

> Tests which invoke `accumulo admin stop ...` fail
> -------------------------------------------------
>
>                 Key: ACCUMULO-3618
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3618
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Eric Newton
>            Priority: Critical
>             Fix For: 1.7.0
>
>
> I'm noticing that all of the tests which are stopping a tabletserver gracefully are failing
for me:
> * SslWithClientAuthIT.adminStop
> * ShutdownIT.adminStop
> * SslIT.adminStop
> It failed locally in addition to on a Jenkins instance. I dug into it locally a little
bit: the FATE operation (ShutdownTServer) never finishes because the TabletServer which is
requested to be shutdown never gets all of its tablets unassigned.
> I haven't been able to figure out why exactly the master didn't move all of the tablets
away.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message