[jira] [Created] (HDFS-6108) make the length of the range in sync_file_range() configurable

Liang Xie created HDFS-6108: --- Summary: make the length of the range in sync_file_range() configurable Key: HDFS-6108 URL: https://issues.apache.org/jira/browse/HDFS-6108 Project: Hadoop HDFS

[jira] [Updated] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang Xie updated HDFS-6108: Status: Patch Available (was: Open) make the length of the range in sync_file_range() configurable

[jira] [Updated] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang Xie updated HDFS-6108: Attachment: HDFS-6108.txt Minor change without new case make the length of the range in sync_file_range()

[jira] [Commented] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937513#comment-13937513 ] haosdent commented on HDFS-6108: Do you mean this method in NativeIO? {code} public static

[jira] [Commented] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937517#comment-13937517 ] Liang Xie commented on HDFS-6108: - yeh:) The nbytes parameter is hard code right now.

[jira] [Created] (HDFS-6109) let sync_file_range() system call run in backgroud

Liang Xie created HDFS-6109: --- Summary: let sync_file_range() system call run in backgroud Key: HDFS-6109 URL: https://issues.apache.org/jira/browse/HDFS-6109 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-6109) let sync_file_range() system call run in backgroud

[ https://issues.apache.org/jira/browse/HDFS-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937601#comment-13937601 ] Liang Xie commented on HDFS-6109: - I will upload this minor patch after HDFS-6108 done, i

[jira] [Commented] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937624#comment-13937624 ] Hadoop QA commented on HDFS-6108: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937636#comment-13937636 ] haosdent commented on HDFS-6108: As you mentioned, different scenario probably has a

[jira] [Commented] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937643#comment-13937643 ] Liang Xie commented on HDFS-6108: - bq. Set a fixed value in hdfs-site.xml or Configuration

[jira] [Updated] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang Xie updated HDFS-6108: Attachment: HDFS-6108-v2.txt Fixed the findbug warning and failure case. make the length of the range in

[jira] [Updated] (HDFS-6068) Disallow snapshot names that are also invalid directory names

[ https://issues.apache.org/jira/browse/HDFS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sathish updated HDFS-6068: -- Attachment: HDFS-6068-0003.patch Disallow snapshot names that are also invalid directory names

[jira] [Commented] (HDFS-6068) Disallow snapshot names that are also invalid directory names

[ https://issues.apache.org/jira/browse/HDFS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937710#comment-13937710 ] sathish commented on HDFS-6068: --- Thanks Nicholas and andrew for having a look on the patch.

[jira] [Commented] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937786#comment-13937786 ] Hadoop QA commented on HDFS-6108: - {color:green}+1 overall{color}. Here are the results of

[jira] [Created] (HDFS-6111) Avoid duplicate entries in Block Scan verification logs

Vinayakumar B created HDFS-6111: --- Summary: Avoid duplicate entries in Block Scan verification logs Key: HDFS-6111 URL: https://issues.apache.org/jira/browse/HDFS-6111 Project: Hadoop HDFS

[jira] [Updated] (HDFS-6111) Avoid duplicate entries in Block Scan verification logs

[ https://issues.apache.org/jira/browse/HDFS-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-6111: Description: Duplicate entries could be generated in datanode verification logs if the datanode

[jira] [Commented] (HDFS-6068) Disallow snapshot names that are also invalid directory names

[ https://issues.apache.org/jira/browse/HDFS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937870#comment-13937870 ] Hadoop QA commented on HDFS-6068: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-6110) adding more slow action log in critical write path

[ https://issues.apache.org/jira/browse/HDFS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938065#comment-13938065 ] Todd Lipcon commented on HDFS-6110: --- Is this duplicate of HDFS-3751? adding more slow

[jira] [Commented] (HDFS-6087) Unify HDFS write/append/truncate

[ https://issues.apache.org/jira/browse/HDFS-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938070#comment-13938070 ] Todd Lipcon commented on HDFS-6087: --- Even creating a new hard link on every hflush is a

[jira] [Commented] (HDFS-6094) The same block can be counted twice towards safe mode threshold

[ https://issues.apache.org/jira/browse/HDFS-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938081#comment-13938081 ] Jing Zhao commented on HDFS-6094: - The latest patch looks good to me. +1. The same block

[jira] [Updated] (HDFS-6094) The same block can be counted twice towards safe mode threshold

[ https://issues.apache.org/jira/browse/HDFS-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-6094: Resolution: Fixed Fix Version/s: 2.4.0 3.0.0 Hadoop Flags: Reviewed

[jira] [Commented] (HDFS-6094) The same block can be counted twice towards safe mode threshold

[ https://issues.apache.org/jira/browse/HDFS-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938095#comment-13938095 ] Hudson commented on HDFS-6094: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5339 (See

[jira] [Updated] (HDFS-6090) Use MiniDFSCluster.Builder instead of deprecated constructors

[ https://issues.apache.org/jira/browse/HDFS-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated HDFS-6090: Target Version/s: 2.5.0 Affects Version/s: 2.3.0 Status: Patch Available (was:

[jira] [Updated] (HDFS-6090) Use MiniDFSCluster.Builder instead of deprecated constructors

[ https://issues.apache.org/jira/browse/HDFS-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated HDFS-6090: Attachment: HDFS-6090.patch Attaching a patch. Use MiniDFSCluster.Builder instead of deprecated

[jira] [Commented] (HDFS-6107) When a block can't be cached due to limited space on the DataNode, that block becomes uncacheable

[ https://issues.apache.org/jira/browse/HDFS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938149#comment-13938149 ] Andrew Wang commented on HDFS-6107: --- In this case I also think we could skip another

[jira] [Commented] (HDFS-6107) When a block can't be cached due to limited space on the DataNode, that block becomes uncacheable

[ https://issues.apache.org/jira/browse/HDFS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938178#comment-13938178 ] Colin Patrick McCabe commented on HDFS-6107: I think it's pretty clear that

[jira] [Commented] (HDFS-6090) Use MiniDFSCluster.Builder instead of deprecated constructors

[ https://issues.apache.org/jira/browse/HDFS-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938182#comment-13938182 ] Jing Zhao commented on HDFS-6090: - Thanks for the cleanup, Akira! The patch looks good to

[jira] [Commented] (HDFS-5516) WebHDFS does not require user name when anonymous http requests are disallowed.

[ https://issues.apache.org/jira/browse/HDFS-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938200#comment-13938200 ] Chris Nauroth commented on HDFS-5516: - +1 for the branch-1 patch too. I'll commit

[jira] [Updated] (HDFS-6107) When a block can't be cached due to limited space on the DataNode, that block becomes uncacheable

[ https://issues.apache.org/jira/browse/HDFS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-6107: --- Resolution: Fixed Fix Version/s: 2.4.0 Status: Resolved (was: Patch

[jira] [Commented] (HDFS-6107) When a block can't be cached due to limited space on the DataNode, that block becomes uncacheable

[ https://issues.apache.org/jira/browse/HDFS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938211#comment-13938211 ] Hudson commented on HDFS-6107: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5341 (See

[jira] [Commented] (HDFS-6107) When a block can't be cached due to limited space on the DataNode, that block becomes uncacheable

[ https://issues.apache.org/jira/browse/HDFS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938232#comment-13938232 ] Hudson commented on HDFS-6107: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5342 (See

[jira] [Updated] (HDFS-6111) Avoid duplicate entries in Block Scan verification logs

[ https://issues.apache.org/jira/browse/HDFS-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-6111: Attachment: HDFS-6111.patch Attached the patch. Please review Avoid duplicate entries in Block

[jira] [Updated] (HDFS-6111) Avoid duplicate entries in Block Scan verification logs

[ https://issues.apache.org/jira/browse/HDFS-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-6111: Target Version/s: 2.4.0 Status: Patch Available (was: Open) Avoid duplicate entries

[jira] [Commented] (HDFS-4564) Webhdfs returns incorrect http response codes for denied operations

[ https://issues.apache.org/jira/browse/HDFS-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938281#comment-13938281 ] Daryn Sharp commented on HDFS-4564: --- I'm working on adapting this and the common half

[jira] [Updated] (HDFS-4513) Clarify WebHDFS REST API that all JSON respsonses may contain additional properties

[ https://issues.apache.org/jira/browse/HDFS-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-4513: -- Resolution: Fixed Fix Version/s: 2.1.1-beta Hadoop Flags: Reviewed

[jira] [Updated] (HDFS-5516) WebHDFS does not require user name when anonymous http requests are disallowed.

[ https://issues.apache.org/jira/browse/HDFS-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-5516: Assignee: Miodrag Radulovic (was: Chris Nauroth) WebHDFS does not require user name when

[jira] [Updated] (HDFS-4814) Configurable DataXceiver thread stack size

[ https://issues.apache.org/jira/browse/HDFS-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-4814: -- Resolution: Won't Fix Status: Resolved (was: Patch Available) Since it only

[jira] [Commented] (HDFS-6090) Use MiniDFSCluster.Builder instead of deprecated constructors

[ https://issues.apache.org/jira/browse/HDFS-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938325#comment-13938325 ] Hadoop QA commented on HDFS-6090: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-5089) When a LayoutVersion support SNAPSHOT, it must support FSIMAGE_NAME_OPTIMIZATION.

[ https://issues.apache.org/jira/browse/HDFS-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938344#comment-13938344 ] Tsz Wo Nicholas Sze commented on HDFS-5089: --- We actually do not plan to backport

[jira] [Commented] (HDFS-5516) WebHDFS does not require user name when anonymous http requests are disallowed.

[ https://issues.apache.org/jira/browse/HDFS-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938349#comment-13938349 ] Hudson commented on HDFS-5516: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5344 (See

[jira] [Commented] (HDFS-6109) let sync_file_range() system call run in backgroud

[ https://issues.apache.org/jira/browse/HDFS-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938356#comment-13938356 ] Colin Patrick McCabe commented on HDFS-6109: If the call to {{sync_file_range}}

[jira] [Updated] (HDFS-5464) Simplify block report diff calculation

[ https://issues.apache.org/jira/browse/HDFS-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-5464: -- Resolution: Won't Fix Status: Resolved (was: Patch Available) The

[jira] [Updated] (HDFS-5470) Add back trunk's reportDiff algorithm to HDFS-2832

[ https://issues.apache.org/jira/browse/HDFS-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-5470: -- Component/s: namenode Add back trunk's reportDiff algorithm to HDFS-2832

[jira] [Updated] (HDFS-5516) WebHDFS does not require user name when anonymous http requests are disallowed.

[ https://issues.apache.org/jira/browse/HDFS-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-5516: Resolution: Fixed Fix Version/s: 2.4.0 1.3.0 1-win

[jira] [Commented] (HDFS-6089) Standby NN while transitioning to active throws a connection refused error when the prior active NN process is suspended

[ https://issues.apache.org/jira/browse/HDFS-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938372#comment-13938372 ] Andrew Wang commented on HDFS-6089: --- Hey Jing, I took a quick look at the patch, few

[jira] [Commented] (HDFS-5089) When a LayoutVersion support SNAPSHOT, it must support FSIMAGE_NAME_OPTIMIZATION.

[ https://issues.apache.org/jira/browse/HDFS-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938379#comment-13938379 ] Hadoop QA commented on HDFS-5089: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-6111) Avoid duplicate entries in Block Scan verification logs

[ https://issues.apache.org/jira/browse/HDFS-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938473#comment-13938473 ] Hadoop QA commented on HDFS-6111: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-6090) Use MiniDFSCluster.Builder instead of deprecated constructors

[ https://issues.apache.org/jira/browse/HDFS-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-6090: Resolution: Fixed Fix Version/s: 2.4.0 Hadoop Flags: Reviewed Status: Resolved (was:

[jira] [Commented] (HDFS-6090) Use MiniDFSCluster.Builder instead of deprecated constructors

[ https://issues.apache.org/jira/browse/HDFS-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938593#comment-13938593 ] Akira AJISAKA commented on HDFS-6090: - Thanks [~jingzhao]! Use MiniDFSCluster.Builder

[jira] [Commented] (HDFS-6090) Use MiniDFSCluster.Builder instead of deprecated constructors

[ https://issues.apache.org/jira/browse/HDFS-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938591#comment-13938591 ] Hudson commented on HDFS-6090: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5349 (See

[jira] [Updated] (HDFS-2832) Enable support for heterogeneous storages in HDFS - DN as a collection of storages

[ https://issues.apache.org/jira/browse/HDFS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-2832: -- Component/s: namenode datanode Assignee: Arpit Agarwal (was:

[jira] [Created] (HDFS-6112) NFS Gateway docs are incorrect for allowed hosts configuration

Aaron T. Myers created HDFS-6112: Summary: NFS Gateway docs are incorrect for allowed hosts configuration Key: HDFS-6112 URL: https://issues.apache.org/jira/browse/HDFS-6112 Project: Hadoop HDFS

[jira] [Commented] (HDFS-6007) Update documentation about short-circuit local reads

[ https://issues.apache.org/jira/browse/HDFS-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938676#comment-13938676 ] Colin Patrick McCabe commented on HDFS-6007: +1. thanks, Masatake Update

[jira] [Updated] (HDFS-6112) NFS Gateway docs are incorrect for allowed hosts configuration

[ https://issues.apache.org/jira/browse/HDFS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-6112: - Attachment: HDFS-6112.patch Patch attached to change the docs slightly. NFS Gateway docs are

[jira] [Updated] (HDFS-6112) NFS Gateway docs are incorrect for allowed hosts configuration

[ https://issues.apache.org/jira/browse/HDFS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-6112: - Status: Patch Available (was: Open) NFS Gateway docs are incorrect for allowed hosts

[jira] [Commented] (HDFS-6112) NFS Gateway docs are incorrect for allowed hosts configuration

[ https://issues.apache.org/jira/browse/HDFS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938680#comment-13938680 ] Todd Lipcon commented on HDFS-6112: --- +1, unless you think we should fix the code to use

[jira] [Commented] (HDFS-6112) NFS Gateway docs are incorrect for allowed hosts configuration

[ https://issues.apache.org/jira/browse/HDFS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938690#comment-13938690 ] Aaron T. Myers commented on HDFS-6112: -- Thanks for the review. I considered that as

[jira] [Commented] (HDFS-6108) make the length of the range in sync_file_range() configurable

[ https://issues.apache.org/jira/browse/HDFS-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938734#comment-13938734 ] Liang Xie commented on HDFS-6108: - Any comments/reviews ? [~cmccabe]/[~tlipcon], i

[jira] [Commented] (HDFS-6109) let sync_file_range() system call run in backgroud

[ https://issues.apache.org/jira/browse/HDFS-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938738#comment-13938738 ] Liang Xie commented on HDFS-6109: - yeh, nice suggestion, especially before i make patch,

[jira] [Commented] (HDFS-6110) adding more slow action log in critical write path

[ https://issues.apache.org/jira/browse/HDFS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938745#comment-13938745 ] Liang Xie commented on HDFS-6110: - seems HDFS-3751 is a superset for current jira ? my

[jira] [Commented] (HDFS-6035) TestCacheDirectives#testCacheManagerRestart is failing on branch-2

[ https://issues.apache.org/jira/browse/HDFS-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938783#comment-13938783 ] sathish commented on HDFS-6035: --- I has tested this in Hadoop-trunk and hadoop-2.3 release

[jira] [Created] (HDFS-6113) Rolling upgrae exception

Fengdong Yu created HDFS-6113: - Summary: Rolling upgrae exception Key: HDFS-6113 URL: https://issues.apache.org/jira/browse/HDFS-6113 Project: Hadoop HDFS Issue Type: Bug Affects Versions:

[jira] [Commented] (HDFS-6112) NFS Gateway docs are incorrect for allowed hosts configuration

[ https://issues.apache.org/jira/browse/HDFS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938804#comment-13938804 ] Hadoop QA commented on HDFS-6112: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-6113) Rolling upgrae exception

[ https://issues.apache.org/jira/browse/HDFS-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938811#comment-13938811 ] Jing Zhao commented on HDFS-6113: - Hi Fengdong, thanks for testing. But hadoop 2.3 does not

[jira] [Comment Edited] (HDFS-6113) Rolling upgrae exception

[ https://issues.apache.org/jira/browse/HDFS-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938811#comment-13938811 ] Jing Zhao edited comment on HDFS-6113 at 3/18/14 4:49 AM: -- Hi

[jira] [Commented] (HDFS-6113) Rolling upgrae exception

[ https://issues.apache.org/jira/browse/HDFS-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938815#comment-13938815 ] Fengdong Yu commented on HDFS-6113: --- [~jingzhao], I know RU is start from 2.4, but

[jira] [Commented] (HDFS-6113) Rolling upgrae exception

[ https://issues.apache.org/jira/browse/HDFS-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938817#comment-13938817 ] Fengdong Yu commented on HDFS-6113: --- continue above, if your answer is yes, then we'd