accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1044) bulk imported files showing up in metadata after bulk import fails
Date Mon, 05 Aug 2013 12:21:55 GMT


ASF subversion and git services commented on ACCUMULO-1044:

Commit ff226a78995057518ac354e671d90f1bb4c30884 in branch refs/heads/master from [~ecn]
[;h=ff226a7 ]


Added many finally clauses to close spans in the presence of exceptions.

I suspect that the extreme depth of the traces is caused by traces that
are started and never stopped.  This most likely happens in the presence
of errors, where exceptions jump around the the span.stop calls.
In particular, when a file is missing for a compaction.  This is known
to occur in 1.4 when bulk imports fail.  See ACCUMULO-1044.

> bulk imported files showing up in metadata after bulk import fails
> ------------------------------------------------------------------
>                 Key: ACCUMULO-1044
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 1.4.2
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Critical
>              Labels: 15_qa_bug
>             Fix For: 1.5.0
> Bulk import fails.  The file is moved to the failures directory.
> But references in the !METADATA table remain.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message