[jira] [Commented] (HADOOP-14543) Should use getAversion() while setting the zkacl
[
https://issues.apache.org/jira/browse/HADOOP-14543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060533#comment-16060533
]
Rakesh R commented on HADOOP-14543:
---
Thanks all for pointing out this, am adding [ZooKeeper user mailing list
discussion
thread|http://zookeeper-user.578899.n2.nabble.com/Version-parameter-passed-to-ZooKeeper-setACL-td7583140.html]
link. The fix looks good to me.
Just curiosity I've tried unit testing this part. Perhaps, you could include
this unit test as well.
{code}
/**
* Test to verify that proper ZooKeper ACLs can be updated on
* ActiveStandbyElector's parent znode.
*/
@Test(timeout = 15000)
public void testSetZooKeeperACLsOnParentZnodeName() throws Exception {
ActiveStandbyElectorCallback cb = Mockito
.mock(ActiveStandbyElectorCallback.class);
ActiveStandbyElector elector = new ActiveStandbyElector(hostPort, 5000,
PARENT_DIR, Ids.READ_ACL_UNSAFE, Collections. emptyList(),
cb, CommonConfigurationKeys.HA_FC_ELECTOR_ZK_OP_RETRIES_DEFAULT);
// Simulate the case by pre-creating znode 'parentZnodeName'. Then updates
// znode's data so that data version will be increased to 1. Here znode's
// aversion is 0.
ZooKeeper otherClient = createClient();
otherClient.create(PARENT_DIR, "sample1".getBytes(), Ids.OPEN_ACL_UNSAFE,
CreateMode.PERSISTENT);
otherClient.setData(PARENT_DIR, "sample2".getBytes(), -1);
otherClient.close();
elector.ensureParentZNode();
}
{code}
> Should use getAversion() while setting the zkacl
>
>
> Key: HADOOP-14543
> URL: https://issues.apache.org/jira/browse/HADOOP-14543
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
> Attachments: HADOOP-14543.patch
>
>
> while setting the zkacl we used {{getVersion()}} which is dataVersion,Ideally
> we should use {{getAversion()}}. If there is any acl changes( i.e relam
> change/..) ,we set the ACL with dataversion which will cause BADVersion and
> *process will not start*. See
> [here|https://issues.apache.org/jira/browse/HDFS-11403?focusedCommentId=16051804=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16051804]
> {{zkClient.setACL(path, zkAcl, stat.getVersion());}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-10075) Update jetty dependency to version 9
[ https://issues.apache.org/jira/browse/HADOOP-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15614361#comment-15614361 ] Rakesh R commented on HADOOP-10075: --- I too faced same problem in my Windows env. I could see the issue has been resolved with this addendum patch and able to continue building. Thanks [~rkanter]. > Update jetty dependency to version 9 > > > Key: HADOOP-10075 > URL: https://issues.apache.org/jira/browse/HADOOP-10075 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 2.2.0, 2.6.0 >Reporter: Robert Rati >Assignee: Robert Kanter >Priority: Critical > Fix For: 3.0.0-alpha2 > > Attachments: HADOOP-10075-002-wip.patch, HADOOP-10075.003.patch, > HADOOP-10075.004.patch, HADOOP-10075.005.patch, HADOOP-10075.006.patch, > HADOOP-10075.007.patch, HADOOP-10075.008.patch, HADOOP-10075.009.patch, > HADOOP-10075.010.patch, HADOOP-10075.011.patch, HADOOP-10075.patch, > HADOOP-10075_addendum.001.patch > > > Jetty6 is no longer maintained. Update the dependency to jetty9. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13201) Print the directory paths when ViewFs denies the rename operation on internal dirs
[
https://issues.apache.org/jira/browse/HADOOP-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15611805#comment-15611805
]
Rakesh R commented on HADOOP-13201:
---
Thank you [~brahmareddy]
> Print the directory paths when ViewFs denies the rename operation on internal
> dirs
> --
>
> Key: HADOOP-13201
> URL: https://issues.apache.org/jira/browse/HADOOP-13201
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
>Affects Versions: 2.7.2
>Reporter: Tianyin Xu
>Assignee: Rakesh R
> Attachments: HADOOP-13201-001.patch, HADOOP-13201.000.patch
>
>
> With ViewFs, the delete and rename operations on internal dirs are denied by
> throwing {{AccessControlException}}.
> Unlike the {{delete()}} which notify the internal dir path, rename does not.
> The attached patch appends the directory path on the logged exception.
> {code:title=ViewFs.java|borderStyle=solid}
> InodeTree.ResolveResult resSrc =
>fsState.resolve(getUriPath(src), false);
> if (resSrc.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + src);
> }
>
> InodeTree.ResolveResult resDst =
> fsState.resolve(getUriPath(dst), false);
> if (resDst.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + dst);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-10829) Iteration on CredentialProviderFactory.serviceLoader is thread-unsafe
[
https://issues.apache.org/jira/browse/HADOOP-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15611750#comment-15611750
]
Rakesh R commented on HADOOP-10829:
---
Thanks [~lmccay],
bq. I am inclined to prefer the approach used in KeyProviderFactory
IIUC, you are suggesting to the use the following way.
{code}
+ // Iterate through the serviceLoader to avoid lazy loading.
+ // Lazy loading would require synchronization in concurrent use cases.
+ static {
+Iterator iterServices =
serviceLoader.iterator();
+while (iterServices.hasNext()) {
+ iterServices.next();
+}
+ }
+
{code}
I had uploaded similar approach in the recent patch
[HADOOP-10829.003.patch|https://issues.apache.org/jira/secure/attachment/12835546/HADOOP-10829.003.patch],
is that ok?
> Iteration on CredentialProviderFactory.serviceLoader is thread-unsafe
> --
>
> Key: HADOOP-10829
> URL: https://issues.apache.org/jira/browse/HADOOP-10829
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
>Affects Versions: 2.6.0
>Reporter: Benoy Antony
>Assignee: Benoy Antony
> Labels: BB2015-05-TBR
> Attachments: HADOOP-10829.003.patch, HADOOP-10829.patch,
> HADOOP-10829.patch
>
>
> CredentialProviderFactory uses _ServiceLoader_ framework to load
> _CredentialProviderFactory_
> {code}
> private static final ServiceLoader serviceLoader
> =
> ServiceLoader.load(CredentialProviderFactory.class);
> {code}
> The _ServiceLoader_ framework does lazy initialization of services which
> makes it thread unsafe. If accessed from multiple threads, it is better to
> synchronize the access.
> Similar synchronization has been done while loading compression codec
> providers via HADOOP-8406.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13201) Print the directory paths when ViewFs denies the rename operation on internal dirs
[
https://issues.apache.org/jira/browse/HADOOP-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15611568#comment-15611568
]
Rakesh R commented on HADOOP-13201:
---
cc/[~vinayrpet]
> Print the directory paths when ViewFs denies the rename operation on internal
> dirs
> --
>
> Key: HADOOP-13201
> URL: https://issues.apache.org/jira/browse/HADOOP-13201
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
>Affects Versions: 2.7.2
>Reporter: Tianyin Xu
>Assignee: Rakesh R
> Attachments: HADOOP-13201-001.patch, HADOOP-13201.000.patch
>
>
> With ViewFs, the delete and rename operations on internal dirs are denied by
> throwing {{AccessControlException}}.
> Unlike the {{delete()}} which notify the internal dir path, rename does not.
> The attached patch appends the directory path on the logged exception.
> {code:title=ViewFs.java|borderStyle=solid}
> InodeTree.ResolveResult resSrc =
>fsState.resolve(getUriPath(src), false);
> if (resSrc.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + src);
> }
>
> InodeTree.ResolveResult resDst =
> fsState.resolve(getUriPath(dst), false);
> if (resDst.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + dst);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13201) Print the directory paths when ViewFs denies the rename operation on internal dirs
[
https://issues.apache.org/jira/browse/HADOOP-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15611496#comment-15611496
]
Rakesh R commented on HADOOP-13201:
---
Kindly review the patch. Thanks!
> Print the directory paths when ViewFs denies the rename operation on internal
> dirs
> --
>
> Key: HADOOP-13201
> URL: https://issues.apache.org/jira/browse/HADOOP-13201
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
>Affects Versions: 2.7.2
>Reporter: Tianyin Xu
>Assignee: Rakesh R
> Attachments: HADOOP-13201-001.patch, HADOOP-13201.000.patch
>
>
> With ViewFs, the delete and rename operations on internal dirs are denied by
> throwing {{AccessControlException}}.
> Unlike the {{delete()}} which notify the internal dir path, rename does not.
> The attached patch appends the directory path on the logged exception.
> {code:title=ViewFs.java|borderStyle=solid}
> InodeTree.ResolveResult resSrc =
>fsState.resolve(getUriPath(src), false);
> if (resSrc.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + src);
> }
>
> InodeTree.ResolveResult resDst =
> fsState.resolve(getUriPath(dst), false);
> if (resDst.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + dst);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-13201) Print the directory paths when ViewFs denies the rename operation on internal dirs
[
https://issues.apache.org/jira/browse/HADOOP-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R reassigned HADOOP-13201:
-
Assignee: Rakesh R
> Print the directory paths when ViewFs denies the rename operation on internal
> dirs
> --
>
> Key: HADOOP-13201
> URL: https://issues.apache.org/jira/browse/HADOOP-13201
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
>Affects Versions: 2.7.2
>Reporter: Tianyin Xu
>Assignee: Rakesh R
> Attachments: HADOOP-13201-001.patch, HADOOP-13201.000.patch
>
>
> With ViewFs, the delete and rename operations on internal dirs are denied by
> throwing {{AccessControlException}}.
> Unlike the {{delete()}} which notify the internal dir path, rename does not.
> The attached patch appends the directory path on the logged exception.
> {code:title=ViewFs.java|borderStyle=solid}
> InodeTree.ResolveResult resSrc =
>fsState.resolve(getUriPath(src), false);
> if (resSrc.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + src);
> }
>
> InodeTree.ResolveResult resDst =
> fsState.resolve(getUriPath(dst), false);
> if (resDst.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + dst);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-10829) Iteration on CredentialProviderFactory.serviceLoader is thread-unsafe
[
https://issues.apache.org/jira/browse/HADOOP-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15611480#comment-15611480
]
Rakesh R commented on HADOOP-10829:
---
Thanks [~benoyantony] for the fix.
+1 (non-binding) for the fix. I've rebased the patch on latest trunk code,
please someone help in reviewing the changes. Thanks!
> Iteration on CredentialProviderFactory.serviceLoader is thread-unsafe
> --
>
> Key: HADOOP-10829
> URL: https://issues.apache.org/jira/browse/HADOOP-10829
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
>Affects Versions: 2.6.0
>Reporter: Benoy Antony
>Assignee: Benoy Antony
> Labels: BB2015-05-TBR
> Attachments: HADOOP-10829.003.patch, HADOOP-10829.patch,
> HADOOP-10829.patch
>
>
> CredentialProviderFactory uses _ServiceLoader_ framework to load
> _CredentialProviderFactory_
> {code}
> private static final ServiceLoader serviceLoader
> =
> ServiceLoader.load(CredentialProviderFactory.class);
> {code}
> The _ServiceLoader_ framework does lazy initialization of services which
> makes it thread unsafe. If accessed from multiple threads, it is better to
> synchronize the access.
> Similar synchronization has been done while loading compression codec
> providers via HADOOP-8406.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-10829) Iteration on CredentialProviderFactory.serviceLoader is thread-unsafe
[
https://issues.apache.org/jira/browse/HADOOP-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-10829:
--
Attachment: HADOOP-10829.003.patch
> Iteration on CredentialProviderFactory.serviceLoader is thread-unsafe
> --
>
> Key: HADOOP-10829
> URL: https://issues.apache.org/jira/browse/HADOOP-10829
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
>Affects Versions: 2.6.0
>Reporter: Benoy Antony
>Assignee: Benoy Antony
> Labels: BB2015-05-TBR
> Attachments: HADOOP-10829.003.patch, HADOOP-10829.patch,
> HADOOP-10829.patch
>
>
> CredentialProviderFactory uses _ServiceLoader_ framework to load
> _CredentialProviderFactory_
> {code}
> private static final ServiceLoader serviceLoader
> =
> ServiceLoader.load(CredentialProviderFactory.class);
> {code}
> The _ServiceLoader_ framework does lazy initialization of services which
> makes it thread unsafe. If accessed from multiple threads, it is better to
> synchronize the access.
> Similar synchronization has been done while loading compression codec
> providers via HADOOP-8406.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13201) Print the directory paths when ViewFs denies the rename operation on internal dirs
[
https://issues.apache.org/jira/browse/HADOOP-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15611154#comment-15611154
]
Rakesh R commented on HADOOP-13201:
---
Thanks [~tianyin] for reporting this. I've modified the exception message and
placed {{src}} and {{dest}} properly, please review this.
> Print the directory paths when ViewFs denies the rename operation on internal
> dirs
> --
>
> Key: HADOOP-13201
> URL: https://issues.apache.org/jira/browse/HADOOP-13201
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
>Affects Versions: 2.7.2
>Reporter: Tianyin Xu
> Attachments: HADOOP-13201-001.patch, HADOOP-13201.000.patch
>
>
> With ViewFs, the delete and rename operations on internal dirs are denied by
> throwing {{AccessControlException}}.
> Unlike the {{delete()}} which notify the internal dir path, rename does not.
> The attached patch appends the directory path on the logged exception.
> {code:title=ViewFs.java|borderStyle=solid}
> InodeTree.ResolveResult resSrc =
>fsState.resolve(getUriPath(src), false);
> if (resSrc.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + src);
> }
>
> InodeTree.ResolveResult resDst =
> fsState.resolve(getUriPath(dst), false);
> if (resDst.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + dst);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13201) Print the directory paths when ViewFs denies the rename operation on internal dirs
[
https://issues.apache.org/jira/browse/HADOOP-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13201:
--
Attachment: HADOOP-13201-001.patch
> Print the directory paths when ViewFs denies the rename operation on internal
> dirs
> --
>
> Key: HADOOP-13201
> URL: https://issues.apache.org/jira/browse/HADOOP-13201
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
>Affects Versions: 2.7.2
>Reporter: Tianyin Xu
> Attachments: HADOOP-13201-001.patch, HADOOP-13201.000.patch
>
>
> With ViewFs, the delete and rename operations on internal dirs are denied by
> throwing {{AccessControlException}}.
> Unlike the {{delete()}} which notify the internal dir path, rename does not.
> The attached patch appends the directory path on the logged exception.
> {code:title=ViewFs.java|borderStyle=solid}
> InodeTree.ResolveResult resSrc =
>fsState.resolve(getUriPath(src), false);
> if (resSrc.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + src);
> }
>
> InodeTree.ResolveResult resDst =
> fsState.resolve(getUriPath(dst), false);
> if (resDst.isInternalDir()) {
>throw new AccessControlException(
> - "Cannot Rename within internal dirs of mount table: it is
> readOnly");
> + "Cannot Rename within internal dirs of mount table: it is readOnly"
> + + dst);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13715) Add isErasureCoded() API to FileStatus class
[
https://issues.apache.org/jira/browse/HADOOP-13715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574080#comment-15574080
]
Rakesh R commented on HADOOP-13715:
---
Thanks [~drankye] for the useful thoughts. I could see encryption feature has
exposed APIs like, HdfsFileStatus has {{#getFileEncryptionInfo()}} exposed and
FileStatus contains {{#isEncrypted()}} flag, to tell whether the underlying
file or directory is encrypted or not. imho, EC could expose APIs in similar
lines.
> Add isErasureCoded() API to FileStatus class
>
>
> Key: HADOOP-13715
> URL: https://issues.apache.org/jira/browse/HADOOP-13715
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs
>Affects Versions: 3.0.0-alpha1
>Reporter: Wei-Chiu Chuang
>Assignee: Wei-Chiu Chuang
>
> Per the discussion in
> [HDFS-10971|https://issues.apache.org/jira/browse/HDFS-10971?focusedCommentId=15567108=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15567108]
> I would like to add a new API {{isErasureCoded()}} to {{FileStatus}} so that
> tools and downstream applications can tell if it needs to treat a file
> differently.
> Hadoop tools that can benefit from this effort include: distcp and
> teragen/terasort.
> Downstream applications such as flume or hbase may also benefit from it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13469) Fix TestRefreshUserMappings.testRefreshSuperUserGroupsConfiguration test failure
[
https://issues.apache.org/jira/browse/HADOOP-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13469:
--
Component/s: test
> Fix TestRefreshUserMappings.testRefreshSuperUserGroupsConfiguration test
> failure
>
>
> Key: HADOOP-13469
> URL: https://issues.apache.org/jira/browse/HADOOP-13469
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
>Reporter: Rakesh R
>Assignee: Rakesh R
>
> This jira is to analyse and fix the test case failure, which is failing in
> Jenkins build,
> [Build_16326|https://builds.apache.org/job/PreCommit-HDFS-Build/16326/testReport/org.apache.hadoop.security/TestRefreshUserMappings/testRefreshSuperUserGroupsConfiguration/]
> very frequently.
> {code}
> Error Message
> first auth for user2 should've succeeded: User: super_userL is not allowed to
> impersonate userL2
> Stacktrace
> java.lang.AssertionError: first auth for user2 should've succeeded: User:
> super_userL is not allowed to impersonate userL2
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.hadoop.security.TestRefreshUserMappings.testRefreshSuperUserGroupsConfiguration(TestRefreshUserMappings.java:200)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-13469) Fix TestRefreshUserMappings.testRefreshSuperUserGroupsConfiguration test failure
Rakesh R created HADOOP-13469:
-
Summary: Fix
TestRefreshUserMappings.testRefreshSuperUserGroupsConfiguration test failure
Key: HADOOP-13469
URL: https://issues.apache.org/jira/browse/HADOOP-13469
Project: Hadoop Common
Issue Type: Bug
Reporter: Rakesh R
Assignee: Rakesh R
This jira is to analyse and fix the test case failure, which is failing in
Jenkins build,
[Build_16326|https://builds.apache.org/job/PreCommit-HDFS-Build/16326/testReport/org.apache.hadoop.security/TestRefreshUserMappings/testRefreshSuperUserGroupsConfiguration/]
very frequently.
{code}
Error Message
first auth for user2 should've succeeded: User: super_userL is not allowed to
impersonate userL2
Stacktrace
java.lang.AssertionError: first auth for user2 should've succeeded: User:
super_userL is not allowed to impersonate userL2
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.hadoop.security.TestRefreshUserMappings.testRefreshSuperUserGroupsConfiguration(TestRefreshUserMappings.java:200)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375137#comment-15375137
]
Rakesh R commented on HADOOP-13366:
---
Thank you [~templedf] for the feedback.
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch, HADOOP-13366-03.patch, HADOOP-13366-04.patch,
> HADOOP-13366-05.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374909#comment-15374909
]
Rakesh R commented on HADOOP-13366:
---
[~ajisakaa], I got a better QA report now:)
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch, HADOOP-13366-03.patch, HADOOP-13366-04.patch,
> HADOOP-13366-05.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: HADOOP-13366-05.patch
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch, HADOOP-13366-03.patch, HADOOP-13366-04.patch,
> HADOOP-13366-05.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: HADOOP-13366-04.patch
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch, HADOOP-13366-03.patch, HADOOP-13366-04.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374514#comment-15374514
]
Rakesh R commented on HADOOP-13366:
---
Attached another patch to resolve the javadoc warnings.
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch, HADOOP-13366-03.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: HADOOP-13366-03.patch
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch, HADOOP-13366-03.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374382#comment-15374382
]
Rakesh R commented on HADOOP-13366:
---
[~ajisakaa], Uploaded new patch with the suggested changes. Please take a look
at it again. Thanks!
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: HADOOP-13366-02.patch
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch,
> HADOOP-13366-02.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: HADOOP-13366-02.patch
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: (was: HADOOP-13366-02.patch)
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374277#comment-15374277
]
Rakesh R commented on HADOOP-13366:
---
Test case failure is unrelated, please ignore it. HADOOP-12588 is addressing
the failure test.
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374204#comment-15374204
]
Rakesh R edited comment on HADOOP-13366 at 7/13/16 2:42 AM:
Thank you [~ajisakaa] for the reviews. Attached new patch addressing the
comments. Also, in the latest patch I've corrected {{core-default.xml}} path in
{{CommonConfigurationKeys.java}} file. Kindly review it again.
was (Author: rakeshr):
Thank you [~ajisakaa] for the reviews. Attached new patch addressing the
comments.
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374219#comment-15374219
]
Rakesh R commented on HADOOP-13366:
---
Thanks [~templedf] for the interest in this. @docRoot tag is used in our
existing hadoop code
[Configuration.java|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java#L121]
and is working fine. Please see [Configuration Api
Doc|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/conf/Configuration.html].
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374204#comment-15374204
]
Rakesh R commented on HADOOP-13366:
---
Thank you [~ajisakaa] for the reviews. Attached new patch addressing the
comments.
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: HADOOP-13366-01.patch
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch, HADOOP-13366-01.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Target Version/s: 2.8.0
Status: Patch Available (was: Open)
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
[
https://issues.apache.org/jira/browse/HADOOP-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-13366:
--
Attachment: HADOOP-13366-00.patch
> Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
> ---
>
> Key: HADOOP-13366
> URL: https://issues.apache.org/jira/browse/HADOOP-13366
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Minor
> Attachments: HADOOP-13366-00.patch
>
>
> This jira is to fix the dead link to {{core-default.xml}} in
> [CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
> javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-13366) Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic javadoc
Rakesh R created HADOOP-13366:
-
Summary: Fix dead link in o.a.h.fs.CommonConfigurationKeysPublic
javadoc
Key: HADOOP-13366
URL: https://issues.apache.org/jira/browse/HADOOP-13366
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Rakesh R
Assignee: Rakesh R
Priority: Minor
This jira is to fix the dead link to {{core-default.xml}} in
[CommonConfigurationKeysPublic|https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/fs/CommonConfigurationKeysPublic.html]
javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-12230) hadoop-project declares duplicate, conflicting curator dependencies
[ https://issues.apache.org/jira/browse/HADOOP-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HADOOP-12230: -- Attachment: HADOOP-12230.branch-2.01.patch > hadoop-project declares duplicate, conflicting curator dependencies > --- > > Key: HADOOP-12230 > URL: https://issues.apache.org/jira/browse/HADOOP-12230 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.7.1 >Reporter: Steve Loughran >Assignee: Rakesh R >Priority: Minor > Attachments: HADOOP-12230-00.patch, HADOOP-12230.branch-2.00.patch, > HADOOP-12230.branch-2.01.patch > > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > HADOOP-11492 bumped up the curator version in trunk & branch-2, but it looks > like there were a couple of extra curator dependencies in branch-2 that > didn't get updated, and are still down as 2.6.0 > This isn't that serious, maven will have picked the latest one, but its still > messy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12230) hadoop-project declares duplicate, conflicting curator dependencies
[ https://issues.apache.org/jira/browse/HADOOP-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940924#comment-14940924 ] Rakesh R commented on HADOOP-12230: --- Thanks again [~ajisakaa] for the detailed review, I didn't notice the duplicate declaration. Attached another patch modifying the same. > hadoop-project declares duplicate, conflicting curator dependencies > --- > > Key: HADOOP-12230 > URL: https://issues.apache.org/jira/browse/HADOOP-12230 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.7.1 >Reporter: Steve Loughran >Assignee: Rakesh R >Priority: Minor > Attachments: HADOOP-12230-00.patch, HADOOP-12230.branch-2.00.patch, > HADOOP-12230.branch-2.01.patch > > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > HADOOP-11492 bumped up the curator version in trunk & branch-2, but it looks > like there were a couple of extra curator dependencies in branch-2 that > didn't get updated, and are still down as 2.6.0 > This isn't that serious, maven will have picked the latest one, but its still > messy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12230) hadoop-project declares duplicate, conflicting curator dependencies
[ https://issues.apache.org/jira/browse/HADOOP-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940672#comment-14940672 ] Rakesh R commented on HADOOP-12230: --- Thank you [~ajisakaa] for the reviews and the help in getting Jenkins report. > hadoop-project declares duplicate, conflicting curator dependencies > --- > > Key: HADOOP-12230 > URL: https://issues.apache.org/jira/browse/HADOOP-12230 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.7.1 >Reporter: Steve Loughran >Assignee: Rakesh R >Priority: Minor > Attachments: HADOOP-12230-00.patch, HADOOP-12230.branch-2.00.patch > > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > HADOOP-11492 bumped up the curator version in trunk & branch-2, but it looks > like there were a couple of extra curator dependencies in branch-2 that > didn't get updated, and are still down as 2.6.0 > This isn't that serious, maven will have picked the latest one, but its still > messy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12230) hadoop-project declares duplicate, conflicting curator dependencies
[
https://issues.apache.org/jira/browse/HADOOP-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936848#comment-14936848
]
Rakesh R commented on HADOOP-12230:
---
Note: The attached patch is based on {{branch2-7}}. I think the patch is
failing because it is trying to apply the patch against {{trunk}}.
> hadoop-project declares duplicate, conflicting curator dependencies
> ---
>
> Key: HADOOP-12230
> URL: https://issues.apache.org/jira/browse/HADOOP-12230
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7.1
>Reporter: Steve Loughran
>Priority: Minor
> Attachments: HADOOP-12230-00.patch
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> HADOOP-11492 bumped up the curator version in trunk & branch-2, but it looks
> like there were a couple of extra curator dependencies in branch-2 that
> didn't get updated, and are still down as 2.6.0
> This isn't that serious, maven will have picked the latest one, but its still
> messy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12230) hadoop-project declares duplicate, conflicting curator dependencies
[ https://issues.apache.org/jira/browse/HADOOP-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HADOOP-12230: -- Attachment: HADOOP-12230-00.patch > hadoop-project declares duplicate, conflicting curator dependencies > --- > > Key: HADOOP-12230 > URL: https://issues.apache.org/jira/browse/HADOOP-12230 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.7.1 >Reporter: Steve Loughran >Priority: Minor > Attachments: HADOOP-12230-00.patch > > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > HADOOP-11492 bumped up the curator version in trunk & branch-2, but it looks > like there were a couple of extra curator dependencies in branch-2 that > didn't get updated, and are still down as 2.6.0 > This isn't that serious, maven will have picked the latest one, but its still > messy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12230) hadoop-project declares duplicate, conflicting curator dependencies
[
https://issues.apache.org/jira/browse/HADOOP-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14935617#comment-14935617
]
Rakesh R commented on HADOOP-12230:
---
Hi [~ste...@apache.org], I could see two occurrences in {{hadoop-project}} and
I'm attaching a patch based on branch-2.7. Kindly review, Thanks!
> hadoop-project declares duplicate, conflicting curator dependencies
> ---
>
> Key: HADOOP-12230
> URL: https://issues.apache.org/jira/browse/HADOOP-12230
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7.1
>Reporter: Steve Loughran
>Priority: Minor
> Attachments: HADOOP-12230-00.patch
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> HADOOP-11492 bumped up the curator version in trunk & branch-2, but it looks
> like there were a couple of extra curator dependencies in branch-2 that
> didn't get updated, and are still down as 2.6.0
> This isn't that serious, maven will have picked the latest one, but its still
> messy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-10584) ActiveStandbyElector goes down if ZK quorum become unavailable
[
https://issues.apache.org/jira/browse/HADOOP-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14591365#comment-14591365
]
Rakesh R commented on HADOOP-10584:
---
Sorry for pitch in late. After looking at the logic, I also feel this case can
occur in the production clusters. On ZooKeeper connection loss
ActiveStandbyElector will do certain number of retries and finally notifies
{{ActiveStandbyElectorCallback#notifyFatalError()}}. I could see the
{{EmbeddedElectorService#notifyFatalError}} implementation is handling the case
by immediately terminating the service. I think we have room to improve this
logic instead of immediately terminating.
About the proposed patch, IIUC it is not required to do an additional handling
of ZooKeeper exceptions and do re-election in ActiveStandbyElector class.
Presently we have {{ActiveStandbyElector#processWatchEvent}} logic to handle
the ZK connection state changes. On connection state changes, ZooKeeper client
will notify this to the registered ZK watcher like, SyncConnected,
Disconnected, Expired etc. Based on the STATE {{ActiveStandbyElector}} is
notifying the registered {{ActiveStandbyElectorCallback}} and does the state
transitions. Please see
[ActiveStandbyElector.java#L550|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ha/ActiveStandbyElector.java#L550]
What I meant is ZooKeeper client will be alive which internally does the
connection re-establishment infinitely. IMHO, we could think of implemeting
{{EmbeddedElectorService#enterNeutralMode}} to handle the NEUTRAL transition of
RM. Also, {{ActiveStandbyElectorCallback#notifyFatalError()}} has to be
refined. Any thoughts?
{code}
public void enterNeutralMode() {
/**
* Possibly due to transient connection issues. Do nothing.
* TODO: Might want to keep track of how long in this state and transition
* to standby.
*/
}
{code}
ActiveStandbyElector goes down if ZK quorum become unavailable
--
Key: HADOOP-10584
URL: https://issues.apache.org/jira/browse/HADOOP-10584
Project: Hadoop Common
Issue Type: Bug
Components: ha
Affects Versions: 2.4.0
Reporter: Karthik Kambatla
Assignee: Karthik Kambatla
Priority: Critical
Attachments: hadoop-10584-prelim.patch, rm.log
ActiveStandbyElector retries operations for a few times. If the ZK quorum
itself is down, it goes down and the daemons will have to be brought up
again.
Instead, it should log the fact that it is unable to talk to ZK, call
becomeStandby on its client, and continue to attempt connecting to ZK.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14544980#comment-14544980
]
Rakesh R commented on HADOOP-11713:
---
Thanks a lot [~cnauroth] for the helpful code review and commit the changes!
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.2.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Fix For: 2.8.0
Attachments: HADOOP-11713-001.patch, HADOOP-11713-002.patch,
HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538422#comment-14538422
]
Rakesh R commented on HADOOP-11713:
---
[~cnauroth] Latest patch addresses the review comments. Please have a look at
it when you get a chance, thanks!
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.2.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Attachments: HADOOP-11713-001.patch, HADOOP-11713-002.patch,
HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-11713:
--
Attachment: HADOOP-11713-002.patch
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.2.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Attachments: HADOOP-11713-001.patch, HADOOP-11713-002.patch,
HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14537606#comment-14537606
]
Rakesh R commented on HADOOP-11713:
---
Attached another patch fixing checkstyle warnings related to my patch. Also,
I've fixed one minor {{whitespace}} and one minor {{checkstyle}} warnings which
are not related to my patch. Since I touched the file I thought of fixing these
considering that the change is very minor and not affecting any functionality.
# whitespace: ChRootedFs.java:381: public void setVerifyChecksum(final boolean
verifyChecksum)
{code}
+ public void setVerifyChecksum(final boolean verifyChecksum)
{code}
# checkstyle: Line is longer than 80 characters (found 81).
{code}
-// Prefix validated at mount time and rest of path validated by mount
target.
+// Prefix validated at mount time and rest of path validated by mount
+// target.
{code}
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.2.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Attachments: HADOOP-11713-001.patch, HADOOP-11713-002.patch,
HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-11713:
--
Attachment: HADOOP-11713-001.patch
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.2.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Attachments: HADOOP-11713-001.patch, HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14537328#comment-14537328
]
Rakesh R commented on HADOOP-11713:
---
Thanks a lot [~cnauroth] for the review comments and the detailed explanation.
Attached another patch addressing the comments.
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.2.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Attachments: HADOOP-11713-001.patch, HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11818) Minor improvements for erasurecode classes
[
https://issues.apache.org/jira/browse/HADOOP-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-11818:
--
Attachment: HADOOP-11818-002.patch
Minor improvements for erasurecode classes
--
Key: HADOOP-11818
URL: https://issues.apache.org/jira/browse/HADOOP-11818
Project: Hadoop Common
Issue Type: Sub-task
Components: io
Reporter: Rakesh R
Assignee: Rakesh R
Attachments: HADOOP-11818-001.patch, HADOOP-11818-002.patch
Following are few observations while going through the {{erasurecode}}
classes.
\\
- Use {{org.slf4j.Logger}} instead of {{org.apache.commons.logging.Log}}
- {{RSErasureDecoder}}, {{RSErasureEncoder}}, {{RSUtil}} missing Apache
License header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11818) Minor improvements for erasurecode classes
[
https://issues.apache.org/jira/browse/HADOOP-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487161#comment-14487161
]
Rakesh R commented on HADOOP-11818:
---
Attached new patch where it modifies link {{ErasureDecoder}} to
{{ErasureCoder}}. Please have a look at it when you get a chance. Thanks!
Minor improvements for erasurecode classes
--
Key: HADOOP-11818
URL: https://issues.apache.org/jira/browse/HADOOP-11818
Project: Hadoop Common
Issue Type: Sub-task
Components: io
Reporter: Rakesh R
Assignee: Rakesh R
Attachments: HADOOP-11818-001.patch, HADOOP-11818-002.patch
Following are few observations while going through the {{erasurecode}}
classes.
\\
- Use {{org.slf4j.Logger}} instead of {{org.apache.commons.logging.Log}}
- {{RSErasureDecoder}}, {{RSErasureEncoder}}, {{RSUtil}} missing Apache
License header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (HADOOP-11818) Minor improvements for erasurecode classes
[
https://issues.apache.org/jira/browse/HADOOP-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-11818 started by Rakesh R.
-
Minor improvements for erasurecode classes
--
Key: HADOOP-11818
URL: https://issues.apache.org/jira/browse/HADOOP-11818
Project: Hadoop Common
Issue Type: Sub-task
Components: io
Reporter: Rakesh R
Assignee: Rakesh R
Attachments: HADOOP-11818-001.patch
Following are few observations while going through the {{erasurecode}}
classes.
\\
- Use {{org.slf4j.Logger}} instead of {{org.apache.commons.logging.Log}}
- {{RSErasureDecoder}}, {{RSErasureEncoder}}, {{RSUtil}} missing Apache
License header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11818) Minor improvements for erasurecode classes
[
https://issues.apache.org/jira/browse/HADOOP-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-11818:
--
Attachment: HADOOP-11818-001.patch
Minor improvements for erasurecode classes
--
Key: HADOOP-11818
URL: https://issues.apache.org/jira/browse/HADOOP-11818
Project: Hadoop Common
Issue Type: Sub-task
Components: io
Reporter: Rakesh R
Assignee: Rakesh R
Attachments: HADOOP-11818-001.patch
Following are few observations while going through the {{erasurecode}}
classes.
\\
- Use {{org.slf4j.Logger}} instead of {{org.apache.commons.logging.Log}}
- {{RSErasureDecoder}}, {{RSErasureEncoder}}, {{RSUtil}} missing Apache
License header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11818) Minor improvements for erasurecode classes
[
https://issues.apache.org/jira/browse/HADOOP-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487140#comment-14487140
]
Rakesh R commented on HADOOP-11818:
---
Thanks [~drankye] for the comment. I hope modify this to below one would be ok,
right?
{code} It implements {@link ErasureCoder}.{code}
Minor improvements for erasurecode classes
--
Key: HADOOP-11818
URL: https://issues.apache.org/jira/browse/HADOOP-11818
Project: Hadoop Common
Issue Type: Sub-task
Components: io
Reporter: Rakesh R
Assignee: Rakesh R
Attachments: HADOOP-11818-001.patch
Following are few observations while going through the {{erasurecode}}
classes.
\\
- Use {{org.slf4j.Logger}} instead of {{org.apache.commons.logging.Log}}
- {{RSErasureDecoder}}, {{RSErasureEncoder}}, {{RSUtil}} missing Apache
License header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-11818) Minor improvements for erasurecode classes
Rakesh R created HADOOP-11818:
-
Summary: Minor improvements for erasurecode classes
Key: HADOOP-11818
URL: https://issues.apache.org/jira/browse/HADOOP-11818
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Rakesh R
Assignee: Rakesh R
Following are few observations while going through the {{erasurecode}} classes.
\\
- Use {{org.slf4j.Logger}} instead of {{org.apache.commons.logging.Log}}
- {{RSErasureDecoder}}, {{RSErasureEncoder}}, {{RSUtil}} missing Apache License
header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11818) Minor improvements for erasurecode classes
[
https://issues.apache.org/jira/browse/HADOOP-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487069#comment-14487069
]
Rakesh R commented on HADOOP-11818:
---
Attached patch which covers these cases. Please review. Thanks!
Minor improvements for erasurecode classes
--
Key: HADOOP-11818
URL: https://issues.apache.org/jira/browse/HADOOP-11818
Project: Hadoop Common
Issue Type: Sub-task
Components: io
Reporter: Rakesh R
Assignee: Rakesh R
Attachments: HADOOP-11818-001.patch
Following are few observations while going through the {{erasurecode}}
classes.
\\
- Use {{org.slf4j.Logger}} instead of {{org.apache.commons.logging.Log}}
- {{RSErasureDecoder}}, {{RSErasureEncoder}}, {{RSUtil}} missing Apache
License header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated HADOOP-11713:
--
Status: Patch Available (was: Open)
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.2.0, 3.0.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Attachments: HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11713) ViewFileSystem should support snapshot methods.
[
https://issues.apache.org/jira/browse/HADOOP-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14362476#comment-14362476
]
Rakesh R commented on HADOOP-11713:
---
Failure reason is, since this is depending on the AbstractFileSystem.java
{{snapshot}} apis in HDFS-5640 patch, we should re-visit this jira after
pushing HDFS-5640 implementation first.
ViewFileSystem should support snapshot methods.
---
Key: HADOOP-11713
URL: https://issues.apache.org/jira/browse/HADOOP-11713
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 3.0.0, 2.2.0
Reporter: Chris Nauroth
Assignee: Rakesh R
Attachments: HDFS-5641-001.patch
Currently, {{ViewFileSystem}} does not dispatch snapshot methods through the
mount table. All snapshot methods throw {{UnsupportedOperationException}},
even though the underlying mount points could be HDFS instances that support
snapshots. We need to update {{ViewFileSystem}} to implement the snapshot
methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11589) NetUtils.createSocketAddr should trim the input URI
[ https://issues.apache.org/jira/browse/HADOOP-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HADOOP-11589: -- Attachment: HADOOP-11589-2.patch NetUtils.createSocketAddr should trim the input URI --- Key: HADOOP-11589 URL: https://issues.apache.org/jira/browse/HADOOP-11589 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.6.0 Reporter: Akira AJISAKA Assignee: Rakesh R Priority: Minor Labels: newbie Attachments: HADOOP-11589-1.patch, HADOOP-11589-2.patch NetUtils.createSocketAddr does not trim the input URI, should be trimmed. HDFS-7684 and HADOOP-9869 are trying to trim some URIs to be passed to the method, however, not all of the inputs have been trimmed already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11589) NetUtils.createSocketAddr should trim the input URI
[ https://issues.apache.org/jira/browse/HADOOP-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14321284#comment-14321284 ] Rakesh R commented on HADOOP-11589: --- Thanks [~brahmareddy], [~umamaheswararao], [~ajisakaa] for the reviews. Attached new patch addressing [~ajisakaa]'s comments. NetUtils.createSocketAddr should trim the input URI --- Key: HADOOP-11589 URL: https://issues.apache.org/jira/browse/HADOOP-11589 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.6.0 Reporter: Akira AJISAKA Assignee: Rakesh R Priority: Minor Labels: newbie Attachments: HADOOP-11589-1.patch, HADOOP-11589-2.patch NetUtils.createSocketAddr does not trim the input URI, should be trimmed. HDFS-7684 and HADOOP-9869 are trying to trim some URIs to be passed to the method, however, not all of the inputs have been trimmed already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HADOOP-11589) NetUtils.createSocketAddr should trim the input URI
[ https://issues.apache.org/jira/browse/HADOOP-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R reassigned HADOOP-11589: - Assignee: Rakesh R NetUtils.createSocketAddr should trim the input URI --- Key: HADOOP-11589 URL: https://issues.apache.org/jira/browse/HADOOP-11589 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.6.0 Reporter: Akira AJISAKA Assignee: Rakesh R Priority: Minor Labels: newbie NetUtils.createSocketAddr does not trim the input URI, should be trimmed. HDFS-7684 and HADOOP-9869 are trying to trim some URIs to be passed to the method, however, not all of the inputs have been trimmed already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11589) NetUtils.createSocketAddr should trim the input URI
[ https://issues.apache.org/jira/browse/HADOOP-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HADOOP-11589: -- Status: Patch Available (was: Open) NetUtils.createSocketAddr should trim the input URI --- Key: HADOOP-11589 URL: https://issues.apache.org/jira/browse/HADOOP-11589 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.6.0 Reporter: Akira AJISAKA Assignee: Rakesh R Priority: Minor Labels: newbie Attachments: HADOOP-11589-1.patch NetUtils.createSocketAddr does not trim the input URI, should be trimmed. HDFS-7684 and HADOOP-9869 are trying to trim some URIs to be passed to the method, however, not all of the inputs have been trimmed already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11589) NetUtils.createSocketAddr should trim the input URI
[ https://issues.apache.org/jira/browse/HADOOP-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HADOOP-11589: -- Attachment: HADOOP-11589-1.patch NetUtils.createSocketAddr should trim the input URI --- Key: HADOOP-11589 URL: https://issues.apache.org/jira/browse/HADOOP-11589 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.6.0 Reporter: Akira AJISAKA Assignee: Rakesh R Priority: Minor Labels: newbie Attachments: HADOOP-11589-1.patch NetUtils.createSocketAddr does not trim the input URI, should be trimmed. HDFS-7684 and HADOOP-9869 are trying to trim some URIs to be passed to the method, however, not all of the inputs have been trimmed already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11589) NetUtils.createSocketAddr should trim the input URI
[ https://issues.apache.org/jira/browse/HADOOP-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14319531#comment-14319531 ] Rakesh R commented on HADOOP-11589: --- Attached patch which does trimming. Please review the patch. Thanks! NetUtils.createSocketAddr should trim the input URI --- Key: HADOOP-11589 URL: https://issues.apache.org/jira/browse/HADOOP-11589 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.6.0 Reporter: Akira AJISAKA Assignee: Rakesh R Priority: Minor Labels: newbie Attachments: HADOOP-11589-1.patch NetUtils.createSocketAddr does not trim the input URI, should be trimmed. HDFS-7684 and HADOOP-9869 are trying to trim some URIs to be passed to the method, however, not all of the inputs have been trimmed already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-6359) NetworkTopology.chooseRandom(..) throws an IllegalArgumentException
[
https://issues.apache.org/jira/browse/HADOOP-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316509#comment-14316509
]
Rakesh R commented on HADOOP-6359:
--
Hi [~szetszwo],
I could see {{numOfDatanodes == 0}} scenario has been taken care. Anything else
needs to be taken care. Otw can we close this?
NetworkTopology.java
{code}
if (numOfDatanodes == 0) {
throw new InvalidTopologyException(
Failed to find datanode (scope=\ + String.valueOf(scope) +
\ excludedScope=\ + String.valueOf(excludedScope) + \).);
}
{code}
NetworkTopology.chooseRandom(..) throws an IllegalArgumentException
---
Key: HADOOP-6359
URL: https://issues.apache.org/jira/browse/HADOOP-6359
Project: Hadoop Common
Issue Type: Bug
Reporter: Tsz Wo Nicholas Sze
Labels: newbie
When numOfDatanodes == 0, NetworkTopology.chooseRandom(..) throws an
IllegalArgumentException.
{noformat}
2009-09-30 00:12:50,768 ERROR org.mortbay.log: /nn_browsedfscontent.jsp
java.lang.IllegalArgumentException: n must be positive
at java.util.Random.nextInt(Random.java:250)
at
org.apache.hadoop.net.NetworkTopology.chooseRandom(NetworkTopology.java:536)
at
org.apache.hadoop.net.NetworkTopology.chooseRandom(NetworkTopology.java:504)
...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-11564) Fix Multithreaded correctness Warnings in BackupImage.java
Rakesh R created HADOOP-11564:
-
Summary: Fix Multithreaded correctness Warnings in BackupImage.java
Key: HADOOP-11564
URL: https://issues.apache.org/jira/browse/HADOOP-11564
Project: Hadoop Common
Issue Type: Bug
Reporter: Rakesh R
Assignee: Rakesh R
Inconsistent synchronization of
org.apache.hadoop.hdfs.server.namenode.BackupImage.namesystem; locked 60% of
time
{code}
Bug type IS2_INCONSISTENT_SYNC (click for details)
In class org.apache.hadoop.hdfs.server.namenode.BackupImage
Field org.apache.hadoop.hdfs.server.namenode.BackupImage.namesystem
Synchronized 60% of the time
Unsynchronized access at BackupImage.java:[line 97]
Unsynchronized access at BackupImage.java:[line 261]
Synchronized access at BackupImage.java:[line 197]
Synchronized access at BackupImage.java:[line 212]
Synchronized access at BackupImage.java:[line 295]
{code}
https://builds.apache.org/job/PreCommit-HDFS-Build/9493//artifact/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html#Details
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-9645) KerberosAuthenticator NPEs on connect error
[
https://issues.apache.org/jira/browse/HADOOP-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14307217#comment-14307217
]
Rakesh R commented on HADOOP-9645:
--
It looks like this is duplicate of HDFS-3980. Can we mark as duplicate ?
KerberosAuthenticator NPEs on connect error
---
Key: HADOOP-9645
URL: https://issues.apache.org/jira/browse/HADOOP-9645
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.5-alpha
Reporter: Daryn Sharp
Priority: Critical
A NPE occurs if there's a kerberos error during initial connect. In this
case, the NN was using a HTTP service principal with a stale kvno. It causes
webhdfs to fail in a non-user friendly manner by masking the real error from
the user.
{noformat}
java.lang.RuntimeException: java.lang.NullPointerException
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1241)
at
sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2713)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:477)
at
org.apache.hadoop.security.authentication.client.KerberosAuthenticator.isNegotiate(KerberosAuthenticator.java:164)
at
org.apache.hadoop.security.authentication.client.KerberosAuthenticator.authenticate(KerberosAuthenticator.java:140)
at
org.apache.hadoop.security.authentication.client.AuthenticatedURL.openConnection(AuthenticatedURL.java:217)
at
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.openHttpUrlConnection(WebHdfsFileSystem.java:364)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-10101) Update guava dependency to the latest version
[ https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14306854#comment-14306854 ] Rakesh R commented on HADOOP-10101: --- bq. I also checked findbugs are not related. I've attached patch to fix HDFS-7709, kindly review it. Thanks! Update guava dependency to the latest version - Key: HADOOP-10101 URL: https://issues.apache.org/jira/browse/HADOOP-10101 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.2.0, 2.6.0 Reporter: Rakesh R Assignee: Vinayakumar B Attachments: HADOOP-10101-002.patch, HADOOP-10101-004.patch, HADOOP-10101-005.patch, HADOOP-10101-006.patch, HADOOP-10101-007.patch, HADOOP-10101-008.patch, HADOOP-10101-009.patch, HADOOP-10101.patch, HADOOP-10101.patch The existing guava version is 11.0.2 which is quite old. This -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10101) Update guava dependency to the latest version
[ https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299734#comment-14299734 ] Rakesh R commented on HADOOP-10101: --- bq.findbugs warnings all seem unrelated Raised HDFS-7709 to address the findbug warnings Update guava dependency to the latest version - Key: HADOOP-10101 URL: https://issues.apache.org/jira/browse/HADOOP-10101 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.2.0, 2.6.0 Reporter: Rakesh R Assignee: Vinayakumar B Attachments: HADOOP-10101-002.patch, HADOOP-10101-004.patch, HADOOP-10101-005.patch, HADOOP-10101-006.patch, HADOOP-10101-007.patch, HADOOP-10101-008.patch, HADOOP-10101.patch, HADOOP-10101.patch The existing guava version is 11.0.2 which is quite old. This -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052297#comment-14052297 ] Rakesh R commented on HADOOP-10641: --- Hi [~posix4e], bq. zab or zk? ZAB is an fresh project idea and this is in the initial phase. I'm not having much details now. Please follow ZOOKEEPER-1931 to know more on this. Motivation - there could be many use cases where you need a quorum based replication. So fresh thought came up to define consensus algorithm (ZAB) more cleanly so that the users can define their own data models and use ZAB to replicate their own data. Actually after seeing 'Coordination Engine' feature in HDFS, I thought of introducing this new idea. Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch, hadoop-coordination.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045813#comment-14045813 ] Rakesh R commented on HADOOP-10641: --- Thanks [~shv] for the interest on ZAB internship and if everything goes well will try use ZAB as a base for CoordinationEngine. I'll keep an eye on this JIRA to watch the progress. Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027601#comment-14027601 ] Rakesh R commented on HADOOP-10641: --- bq.The intent of this jira is not to solve the general problem of distributed consensus. That is, I do not propose to build an implementation of paxos or other coordination algorithms here. This is only to introduce a common interface, so that real implementations such as ZooKeeper could be plugged into hadoop projects. This sounds interesting. Thanks for the effort!. If I understood the discussion correctly here, the idea is to build a quorum based replication. For example, the events(I think this represents data) are submitted as proposals to a quorum of nodes. In ZooKeeper terms, Leader proposes values to the Followers. Now Leader wait for acknowledgements from a quorum of Followers before considering a proposal committed. Also, Leader queues COMMIT(zxid) events to all Followers so that all other nodes learn the events. This ensures that the events will be reached to all nodes in the system. Adding one more point, in general ZK provides strong ordering guarantees. Sometime back ZooKeeper folks initiated discussions to decouple ZAB from ZooKeeper, so that users can make use of this and can define their own models and reliably replicate the data. There is a related JIRA ZOOKEEPER-1931 talks similar feature, now this is in initial dev stage. Please have a look at this. I hope this would help to define a common interface, also an opportunity for us to know more about the use cases. Regards, Rakesh Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HADOOP-10101) Update guava dependency to the latest version 15.0
Rakesh R created HADOOP-10101: - Summary: Update guava dependency to the latest version 15.0 Key: HADOOP-10101 URL: https://issues.apache.org/jira/browse/HADOOP-10101 Project: Hadoop Common Issue Type: Improvement Reporter: Rakesh R The existing guava version is 11.0.2 which is quite old. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-10101) Update guava dependency to the latest version 15.0
[ https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HADOOP-10101: -- Description: The existing guava version is 11.0.2 which is quite old. This (was: The existing guava version is 11.0.2 which is quite old.) Update guava dependency to the latest version 15.0 -- Key: HADOOP-10101 URL: https://issues.apache.org/jira/browse/HADOOP-10101 Project: Hadoop Common Issue Type: Improvement Reporter: Rakesh R Attachments: HADOOP-10101.patch The existing guava version is 11.0.2 which is quite old. This -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-10101) Update guava dependency to the latest version 15.0
[ https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HADOOP-10101: -- Attachment: HADOOP-10101.patch Update guava dependency to the latest version 15.0 -- Key: HADOOP-10101 URL: https://issues.apache.org/jira/browse/HADOOP-10101 Project: Hadoop Common Issue Type: Improvement Reporter: Rakesh R Attachments: HADOOP-10101.patch The existing guava version is 11.0.2 which is quite old. -- This message was sent by Atlassian JIRA (v6.1#6144)
