Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 3 Jul 2014 01:07:24 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12725075.1404328528106.92955.1404349644630@arcas>
In-Reply-To: <JIRA.12725075.1404328528106@arcas>
References: <JIRA.12725075.1404328528106@arcas>
Subject: [jira] [Updated] (ACCUMULO-2974) Unable to assign single tablet
 table migrated to 1.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-2974:
---------------------------------

    Status: Patch Available  (was: Open)

> Unable to assign single tablet table migrated to 1.6.0
> ------------------------------------------------------
>
>                 Key: ACCUMULO-2974
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2974
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.6.0
>            Reporter: John Vines
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.6.1
>
>         Attachments: 0001-ACCUMULO-2974-Include-the-table-id-when-constructing.patch, badMetaScan.png, goodMetaScan.png, stackTrace.png
>
>
> Sorry for the screen caps, no copy/paste from machines.
> Background- several tables migrated from 1.5.1 to 1.6.0. Only one of which was a single tablet. Upon starting, we noticed that that single table was not loading and the master was reporting an unassigned tablet. Had a stack trace in the monitor (attached).
> Also attached is a a metadata scan of the table in question (ID: 12). I was able to get a functional copy of the table by offlining 12 and cloning it. It functioned without issues. Attached is a copy of it's metadata scan as well (ID: 9o)
> The stack trace leads me to it being a specific issue with the contents of srv:dir, and the only difference is the relative vs. absolute file names. This cluster was not changed to multiple namenodes and ../tables/default_tablet does not exist. There are other tables which still use the relative naming scheme, and the system does not seem to be having issues with them.


--
This message was sent by Atlassian JIRA
(v6.2#6252)