[
https://issues.apache.org/jira/browse/HDFS-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305849#comment-14305849
]
Colin Patrick McCabe edited comment on HDFS-7719 at 2/4/15 8:01 PM:
--------------------------------------------------------------------
+1. Thanks, Eddy
{code}
java.lang.NoClassDefFoundError:
org/apache/hadoop/security/proto/SecurityProtos$GetDelegationTokenRequestProto$1
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
{code}
This looks unrelated. I'm not sure why we see these {{NoClassDefFoundError}}
messages intermittently on Jenkins. The last time we looked into this, it was
an Ansible issue with JDK classes getting moved around during the test run... I
thought we had fixed that though.
was (Author: cmccabe):
+1. Thanks, Eddy
{code}
java.lang.NoClassDefFoundError:
org/apache/hadoop/security/proto/SecurityProtos$GetDelegationTokenRequestProto$1
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
{code}
This looks unrelated. I'm not sure why we see these {{NoClassDefFoundError}}
messages intermittently on Jenkins. The last time we looked into this, it was
a Puppet issue with JDK classes getting moved around during the test run... I
thought we had fixed that though.
> BlockPoolSliceStorage#removeVolumes fails to remove some in-memory state
> associated with volumes
> ------------------------------------------------------------------------------------------------
>
> Key: HDFS-7719
> URL: https://issues.apache.org/jira/browse/HDFS-7719
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Lei (Eddy) Xu
> Assignee: Lei (Eddy) Xu
> Attachments: HDFS-7719.000.patch, HDFS-7719.001.patch,
> HDFS-7719.002.patch, HDFS-7719.003.patch
>
>
> The parameter of {{BlockPoolSliceStorage#removeVolumes()}} is a set of volume
> level directories, thus {{BlockPoolSliceStorage}} could not directly compare
> its own {{StorageDirs}} with this volume-level directory. The result of that
> is {{BlockPoolSliceStorage}} did not actually remove the targeted
> {{StorageDirectory}}.
> It will cause failure when remove a volume and then immediately add a volume
> back with the same mount point..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
