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-3441) Master stuck attempting to assign root tablet to previous session of tserver
Date Fri, 19 Dec 2014 18:52:13 GMT

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

Josh Elser commented on ACCUMULO-3441:
--------------------------------------

Do you have the master logs to verify that the Master was updating its view of tablet servers
{{Master.gatherTableInformation}}?

You should see log messages like {{Finished gathering information from XX servers in XXX seconds}}.
I think that's what's tracking active servers and their sessionIDs. If that was delayed, that's
an easy explanation as to why the Master didn't see the new server.

> Master stuck attempting to assign root tablet to previous session of tserver
> ----------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3441
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3441
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.6.0
>            Reporter: John Vines
>
> Encountered while doing ingest with agitation-
> n3 has the root tablet
> 1:41 - n2 dies, had sessionId 14a5b2f992e0322
> 1:42 - n2 comes back up, new session id 14a5b2f992e03aa
> 2:01 - n3 dies
> 2:03 - master assigns root tablet to n2, but with sessionId 14a5b2f992e0322
> cluster is stuck because root tablet repeatedly fails attempts to issue reload, tablet
never gets reassigned to a new server or the same server with the correct sessionId
> Bouncing the master resolved this



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

Mime
View raw message