accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3276) Shard.xml hung with no client output
Date Thu, 30 Oct 2014 22:41:35 GMT


Josh Elser commented on ACCUMULO-3276:

Alright, I'm stumped (again). I traced through the code as to what the TabletServer would
be doing after it found that there were no WALs for the tablet but before it would have reported
that it was successfully loaded (locally and to the master).

I'm thinking about writing some sort daemon in the tablet server that can watch the monitor
the assignment pools (normal assignments and metadata assignments) and potentially catch this
happening in the future. I don't think I'd want it to do anything that print some information
that the thread is stuck. Interrupting/cancelling the thread would also be a possibility,
but I haven't thought about the repercussions of that (not sure if assignment would gracefully

> Shard.xml hung with no client output
> ------------------------------------
>                 Key: ACCUMULO-3276
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>          Time Spent: 40m
>  Remaining Estimate: 0h
> Ran Shard.xml over a 5 node instance. The only line of client output I got was that ZooSession
connected to the quorum.
> 45 minutes later, my test runner timed out the module. We need more information in the
client test log to actually determine where it got stuck.

This message was sent by Atlassian JIRA

View raw message