accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1321) Dynamic Classloader lost jars
Date Tue, 11 Jun 2013 19:34:19 GMT

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

Keith Turner commented on ACCUMULO-1321:
----------------------------------------

bq. I disagree, this bug is still extant. We just did work which made it less probable, and
this is evidence in 1.5.0 that it's still here.

Are you going to change the affects version to 1.5.0 and the fix version to 1.5.1?  This practice
in general seems really confusing to me, this bug is refed in the 1.5.0 release notes tagged
in svn. 
                
> Dynamic Classloader lost jars
> -----------------------------
>
>                 Key: ACCUMULO-1321
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1321
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: John Vines
>            Priority: Blocker
>             Fix For: 1.5.0
>
>         Attachments: ACCUMULO-1321.patch
>
>
> We have a table setup that uses some custom iterators. We ran an MR job against it without
issues. We then ran the job immediately after the first one wrapped and 2 of my tservers errored
with ClassNotFoundException, even though it ran just fine before.
> Unfortunately we don't have a stack trace (to see if it was breaking differently in the
VFSClassLoader), nor a convenient way to recreate currently. We're working on reproducing
it in order to get more information.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message