[
https://issues.apache.org/jira/browse/ACCUMULO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286797#comment-14286797
]
Eric Newton commented on ACCUMULO-1292:
---------------------------------------
[~dlmarion] I like your change, too. I don't think you can do this:
{noformat}
while (cl == null || cl.getParent() != parent.getClassLoader()) {
{noformat}
if you don't hold the read lock. We are mixing class synchronization with a
Read/Write lock, so it would be easy to miss some other locking issues. If you
are going to hold a write lock while updating class members (and possibly
blocking), how is this that much different from a synchronized method?
Either patch needs a review from at least [~kturner], though I hope a few other
folks would check it out, too.
> Tablet constructor can hang on vfs classloader, preventing tablets from
> loading
> -------------------------------------------------------------------------------
>
> Key: ACCUMULO-1292
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1292
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.5.0, 1.6.0, 1.6.1
> Reporter: John Vines
> Assignee: Eric Newton
> Fix For: 1.7.0, 1.6.3
>
> Attachments: ACCUMULO-1292-using-locks.patch, ACCUMULO-1292.patch
>
>
> Taken from TODO from r1424106 regarding ACCUMULO-867. This is something that
> we should at least look into more before 1.5 is released.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)