[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042133#comment-14042133 ] Konstantin Shvachko commented on HDFS-6469: --- Maysam, most of your questions are

[jira] [Commented] (HDFS-5851) Support memory as a storage medium

[ https://issues.apache.org/jira/browse/HDFS-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047035#comment-14047035 ] Konstantin Shvachko commented on HDFS-5851: --- Few questions as I don't see it

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054545#comment-14054545 ] Konstantin Shvachko commented on HDFS-6469: --- Sanjay, by not increasing journaling

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056634#comment-14056634 ] Konstantin Shvachko commented on HDFS-6469: --- You are right, on the client

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14057235#comment-14057235 ] Konstantin Shvachko commented on HDFS-6469: --- [~atm] requested an answer to Todd's

[jira] [Commented] (HDFS-6584) Support archival storage

[ https://issues.apache.org/jira/browse/HDFS-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14061379#comment-14061379 ] Konstantin Shvachko commented on HDFS-6584: --- The design doc talks about the

[jira] [Resolved] (HDFS-52) SecondaryNameNode should validate the downloaded files.

[ https://issues.apache.org/jira/browse/HDFS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-52. - Resolution: Duplicate This is fixed by HDFS-903 in a more generic way, I believe.

[jira] [Commented] (HDFS-333) A State Machine for name-node blocks.

[ https://issues.apache.org/jira/browse/HDFS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069249#comment-14069249 ] Konstantin Shvachko commented on HDFS-333: -- It is still valid. It would formalize

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069598#comment-14069598 ] Konstantin Shvachko commented on HDFS-6469: --- ??to be practical it needs to be an

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069597#comment-14069597 ] Konstantin Shvachko commented on HDFS-6469: --- ??A customer can use just QJM (which

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069612#comment-14069612 ] Konstantin Shvachko commented on HDFS-6469: --- Sanjay, the discussion can go on for

[jira] [Resolved] (HDFS-272) Update startup scripts to start Checkpoint node instead of SecondaryNameNode

[ https://issues.apache.org/jira/browse/HDFS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-272. -- Resolution: Won't Fix Resolving. It was created when SNN was deprecated. Now that SNN is

[jira] [Commented] (HDFS-6134) Transparent data at rest encryption

[ https://issues.apache.org/jira/browse/HDFS-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14105694#comment-14105694 ] Konstantin Shvachko commented on HDFS-6134: --- Guys, looks like you ignored javac

[jira] [Commented] (HDFS-6938) Cleanup javac warnings in FSNamesystem.java

[ https://issues.apache.org/jira/browse/HDFS-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109668#comment-14109668 ] Konstantin Shvachko commented on HDFS-6938: --- +1 looks good. Cleanup javac

[jira] [Created] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

Konstantin Shvachko created HDFS-6940: - Summary: Initial refactoring to allow ConsensusNode implementation Key: HDFS-6940 URL: https://issues.apache.org/jira/browse/HDFS-6940 Project: Hadoop HDFS

[jira] [Updated] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6940: -- Attachment: HDFS-6940.patch Here is the patch. Aaron, what are the reservations?

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110057#comment-14110057 ] Konstantin Shvachko commented on HDFS-6469: --- Heads up on further actions. The

[jira] [Commented] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110081#comment-14110081 ] Konstantin Shvachko commented on HDFS-6940: --- I'd be much more comfortable with

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14120723#comment-14120723 ] Konstantin Shvachko commented on HDFS-6469: --- Thanks for the thoughts, Sanjay. I

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14120771#comment-14120771 ] Konstantin Shvachko commented on HDFS-6469: --- Sanjay, we have been back and forth

[jira] [Assigned] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko reassigned HDFS-3107: - Assignee: Plamen Jeliazkov Nicholas in [his

[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14123764#comment-14123764 ] Konstantin Shvachko commented on HDFS-3107: --- No, while under recovery the file

[jira] [Updated] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6940: -- Status: Patch Available (was: Open) ATM Not entirely sure what was unclear here.

[jira] [Created] (HDFS-7007) Interfaces to plugin ConsensusNode.

Konstantin Shvachko created HDFS-7007: - Summary: Interfaces to plugin ConsensusNode. Key: HDFS-7007 URL: https://issues.apache.org/jira/browse/HDFS-7007 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-7007) Interfaces to plugin ConsensusNode.

[ https://issues.apache.org/jira/browse/HDFS-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14123844#comment-14123844 ] Konstantin Shvachko commented on HDFS-7007: --- [~sanjay.radia]

[jira] [Commented] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14123858#comment-14123858 ] Konstantin Shvachko commented on HDFS-6940: --- Aaron, I created HDFS-7007 we can

[jira] [Commented] (HDFS-7007) Interfaces to plugin ConsensusNode.

[ https://issues.apache.org/jira/browse/HDFS-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14123884#comment-14123884 ] Konstantin Shvachko commented on HDFS-7007: --- Another

[jira] [Updated] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6940: -- Resolution: Fixed Fix Version/s: 2.6.0 Status: Resolved (was: Patch

[jira] [Commented] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125876#comment-14125876 ] Konstantin Shvachko commented on HDFS-6940: --- why doing this refactor, which is

[jira] [Commented] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125877#comment-14125877 ] Konstantin Shvachko commented on HDFS-6940: --- Suresh, this patch was up for review

[jira] [Commented] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125881#comment-14125881 ] Konstantin Shvachko commented on HDFS-6940: --- Todd, I think your comment really

[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126103#comment-14126103 ] Konstantin Shvachko commented on HDFS-3107: --- Yes, I think it is. You cannot

[jira] [Commented] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127227#comment-14127227 ] Konstantin Shvachko commented on HDFS-6940: --- Chris, could you please take a look

[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127371#comment-14127371 ] Konstantin Shvachko commented on HDFS-3107: --- I see your point. I'll let Plamen

[jira] [Reopened] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko reopened HDFS-6940: --- I just reverted it. Initial refactoring to allow ConsensusNode implementation

[jira] [Commented] (HDFS-6940) Initial refactoring to allow ConsensusNode implementation

[ https://issues.apache.org/jira/browse/HDFS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127866#comment-14127866 ] Konstantin Shvachko commented on HDFS-6940: --- Todd could you please comment on the

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273669#comment-13273669 ] Konstantin Shvachko commented on HDFS-3368: --- d01, do2, do3 are chosen for adding

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278968#comment-13278968 ] Konstantin Shvachko commented on HDFS-3368: --- You are right a failure of three

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279247#comment-13279247 ] Konstantin Shvachko commented on HDFS-3368: --- This is pretty rare but when you hit

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279368#comment-13279368 ] Konstantin Shvachko commented on HDFS-3368: --- Thanks for the review. Name change

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13280418#comment-13280418 ] Konstantin Shvachko commented on HDFS-3368: --- I incorporated Nicholas's comments.

[jira] [Updated] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-3368: -- Status: Open (was: Patch Available) Missing blocks due to bad DataNodes comming

[jira] [Created] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

Konstantin Shvachko created HDFS-3462: - Summary: TestDFSClientRetries.busyTest() should restore default xceiver count in the config. Key: HDFS-3462 URL: https://issues.apache.org/jira/browse/HDFS-3462

[jira] [Updated] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

[ https://issues.apache.org/jira/browse/HDFS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-3462: -- Attachment: testGetFileChecksum.log.htm Attaching log from Jenkins build for HDFS-3368

[jira] [Created] (HDFS-3463) DFSTestUtil.waitCorruptReplicas() should not use file reading time as a timeout measure.

Konstantin Shvachko created HDFS-3463: - Summary: DFSTestUtil.waitCorruptReplicas() should not use file reading time as a timeout measure. Key: HDFS-3463 URL: https://issues.apache.org/jira/browse/HDFS-3463

[jira] [Updated] (HDFS-3463) DFSTestUtil.waitCorruptReplicas() should not use file reading time as a timeout measure.

[ https://issues.apache.org/jira/browse/HDFS-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-3463: -- Attachment: testBlockCorruptionRecoveryPolicy1.log.htm Attaching log from Jenkins build

[jira] [Commented] (HDFS-3463) DFSTestUtil.waitCorruptReplicas() should not use file reading time as a timeout measure.

[ https://issues.apache.org/jira/browse/HDFS-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13283184#comment-13283184 ] Konstantin Shvachko commented on HDFS-3463: ---

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13283197#comment-13283197 ] Konstantin Shvachko commented on HDFS-3368: --- I committed to trunk and

[jira] [Updated] (HDFS-3368) Missing blocks due to bad DataNodes coming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-3368: -- Target Version/s: 2.0.0-alpha, 0.22.1, 3.0.0 (was: 0.22.1, 2.0.0-alpha, 3.0.0)

[jira] [Updated] (HDFS-3368) Missing blocks due to bad DataNodes coming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-3368: -- Resolution: Fixed Status: Resolved (was: Patch Available) Resolving. Thanks

[jira] [Commented] (HDFS-3463) DFSTestUtil.waitCorruptReplicas() should not use file reading time as a timeout measure.

[ https://issues.apache.org/jira/browse/HDFS-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285463#comment-13285463 ] Konstantin Shvachko commented on HDFS-3463: --- Agreed, these are the same. Thanks

[jira] [Commented] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

[ https://issues.apache.org/jira/browse/HDFS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285488#comment-13285488 ] Konstantin Shvachko commented on HDFS-3462: --- +int originalXcievers =

[jira] [Resolved] (HDFS-3402) Fix hdfs script for for secure datanodes

[ https://issues.apache.org/jira/browse/HDFS-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-3402. --- Resolution: Fixed Hadoop Flags: Reviewed +1 I just committed this to branch

[jira] [Resolved] (HDFS-3403) SecondaryNamenode doesn't start up in secure cluster

[ https://issues.apache.org/jira/browse/HDFS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-3403. --- Resolution: Fixed Hadoop Flags: Reviewed +1 I just committed this to branch

[jira] [Commented] (HDFS-1860) when renewing/canceling DelegationToken over http we need to pass exception information back to the caller.

[ https://issues.apache.org/jira/browse/HDFS-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289129#comment-13289129 ] Konstantin Shvachko commented on HDFS-1860: --- I just committed this to branch

[jira] [Updated] (HDFS-1584) Need to check TGT and renew if needed when fetching delegation tokens using HFTP

[ https://issues.apache.org/jira/browse/HDFS-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-1584: -- Affects Version/s: 0.22.0 Fix Version/s: 0.22.1 Assignee: Benoy

[jira] [Commented] (HDFS-3493) Replication is not happened for the block (which is recovered and in finalized) to the Datanode which has got the same block with old generation timestamp in RBW

[ https://issues.apache.org/jira/browse/HDFS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289608#comment-13289608 ] Konstantin Shvachko commented on HDFS-3493: --- I agree with Uma this works as

[jira] [Assigned] (HDFS-3370) HDFS hardlink

[ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko reassigned HDFS-3370: - Assignee: Konstantin Shvachko (was: Liyin Tang) HDFS hardlink

[jira] [Assigned] (HDFS-3370) HDFS hardlink

[ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko reassigned HDFS-3370: - Assignee: Liyin Tang (was: Konstantin Shvachko) Sorry some combination of

[jira] [Commented] (HDFS-3370) HDFS hardlink

[ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294229#comment-13294229 ] Konstantin Shvachko commented on HDFS-3370: --- I would recommend finding a

[jira] [Commented] (HDFS-3370) HDFS hardlink

[ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13396306#comment-13396306 ] Konstantin Shvachko commented on HDFS-3370: --- the key question: What services

[jira] [Commented] (HDFS-3370) HDFS hardlink

[ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397700#comment-13397700 ] Konstantin Shvachko commented on HDFS-3370: --- Sanjay, you are taking a quote out

[jira] [Commented] (HDFS-3370) HDFS hardlink

[ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405142#comment-13405142 ] Konstantin Shvachko commented on HDFS-3370: --- Jesse, thanks for the detailed

[jira] [Commented] (HDFS-3586) Blocks are not getting replicate even DN's are availble.

[ https://issues.apache.org/jira/browse/HDFS-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405404#comment-13405404 ] Konstantin Shvachko commented on HDFS-3586: --- Uma, I think that the RBW replicas

[jira] [Commented] (HDFS-3586) Blocks are not getting replicate even DN's are availble.

[ https://issues.apache.org/jira/browse/HDFS-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406314#comment-13406314 ] Konstantin Shvachko commented on HDFS-3586: --- So you propose to sacrifice a

[jira] [Commented] (HDFS-3370) HDFS hardlink

[ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406322#comment-13406322 ] Konstantin Shvachko commented on HDFS-3370: --- to leverage ZooKeeper Correct.

[jira] [Commented] (HDFS-3772) HDFS NN will hang in safe mode and never come out if we change the dfs.namenode.replication.min bigger.

[ https://issues.apache.org/jira/browse/HDFS-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434293#comment-13434293 ] Konstantin Shvachko commented on HDFS-3772: --- I was writing this when Jira went

[jira] [Commented] (HDFS-3772) HDFS NN will hang in safe mode and never come out if we change the dfs.namenode.replication.min bigger.

[ https://issues.apache.org/jira/browse/HDFS-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434913#comment-13434913 ] Konstantin Shvachko commented on HDFS-3772: --- What problem are you solving?

[jira] [Commented] (HDFS-3772) HDFS NN will hang in safe mode and never come out if we change the dfs.namenode.replication.min bigger.

[ https://issues.apache.org/jira/browse/HDFS-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435307#comment-13435307 ] Konstantin Shvachko commented on HDFS-3772: --- It is not the hang. It works as

[jira] [Commented] (HDFS-3772) HDFS NN will hang in safe mode and never come out if we change the dfs.namenode.replication.min bigger.

[ https://issues.apache.org/jira/browse/HDFS-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435321#comment-13435321 ] Konstantin Shvachko commented on HDFS-3772: --- And you can use {code}hadoop

[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=13934316#comment-13934316 ] Konstantin Shvachko commented on HDFS-6087: --- Not sure I fully understood what you

[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=13935686#comment-13935686 ] Konstantin Shvachko commented on HDFS-6087: --- Based on what you write, I see two

[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=13935727#comment-13935727 ] Konstantin Shvachko commented on HDFS-6087: --- If it does copy-on-write, then the

[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=13946968#comment-13946968 ] Konstantin Shvachko commented on HDFS-6087: --- Guo, could you please clarify. Are

[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=13948814#comment-13948814 ] Konstantin Shvachko commented on HDFS-6087: --- Currently, block recovery is very

[jira] [Commented] (HDFS-4114) Remove the BackupNode and CheckpointNode from trunk

[ https://issues.apache.org/jira/browse/HDFS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13967774#comment-13967774 ] Konstantin Shvachko commented on HDFS-4114: --- I'll commit it to trunk this

[jira] [Commented] (HDFS-4114) Remove the BackupNode and CheckpointNode from trunk

[ https://issues.apache.org/jira/browse/HDFS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13976091#comment-13976091 ] Konstantin Shvachko commented on HDFS-4114: --- [~sureshms]. # I thought I answered

[jira] [Commented] (HDFS-4114) Remove the BackupNode and CheckpointNode from trunk

[ https://issues.apache.org/jira/browse/HDFS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13977912#comment-13977912 ] Konstantin Shvachko commented on HDFS-4114: --- Sure thing. Please assign them to me

[jira] [Commented] (HDFS-6271) Rename JournalProtocol to BackupNodeJournalProtocol

[ https://issues.apache.org/jira/browse/HDFS-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979136#comment-13979136 ] Konstantin Shvachko commented on HDFS-6271: --- [~sureshms] is this jira intended

[jira] [Created] (HDFS-6325) Append should fail if the last block has unsufficient number of replicas

Konstantin Shvachko created HDFS-6325: - Summary: Append should fail if the last block has unsufficient number of replicas Key: HDFS-6325 URL: https://issues.apache.org/jira/browse/HDFS-6325

[jira] [Commented] (HDFS-6325) Append should fail if the last block has unsufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988209#comment-13988209 ] Konstantin Shvachko commented on HDFS-6325: --- An easy way to reproduce this is to

[jira] [Updated] (HDFS-6325) Append should fail if the last block has unsufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6325: -- Fix Version/s: (was: 2.5.0) Append should fail if the last block has unsufficient

[jira] [Updated] (HDFS-6325) Append should fail if the last block has unsufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6325: -- Target Version/s: 2.5.0 Append should fail if the last block has unsufficient number

[jira] [Updated] (HDFS-6325) Append should fail if the last block has insufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6325: -- Summary: Append should fail if the last block has insufficient number of replicas

[jira] [Commented] (HDFS-6325) Append should fail if the last block has insufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994738#comment-13994738 ] Konstantin Shvachko commented on HDFS-6325: --- Patch review comments: # Need to

[jira] [Commented] (HDFS-6325) Append should fail if the last block has insufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994737#comment-13994737 ] Konstantin Shvachko commented on HDFS-6325: --- Here are some thoughts after

[jira] [Updated] (HDFS-6325) Append should fail if the last block has insufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6325: -- Target Version/s: 2.4.1 (was: 2.5.0) Append should fail if the last block has

[jira] [Commented] (HDFS-6325) Append should fail if the last block has insufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999637#comment-13999637 ] Konstantin Shvachko commented on HDFS-6325: --- +1 looks good. Append should fail

[jira] [Commented] (HDFS-6325) Append should fail if the last block has insufficient number of replicas

[ https://issues.apache.org/jira/browse/HDFS-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998517#comment-13998517 ] Konstantin Shvachko commented on HDFS-6325: --- This looks good. Just two final

[jira] [Created] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

Konstantin Shvachko created HDFS-6469: - Summary: Coordinated replication of the namespace using ConsensusNode Key: HDFS-6469 URL: https://issues.apache.org/jira/browse/HDFS-6469 Project: Hadoop

[jira] [Updated] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-6469: -- Attachment: CNodeDesign.pdf In a nutshell. Namespace updates are initiated on one of

[jira] [Closed] (HDFS-2064) Warm HA NameNode going Hot

[ https://issues.apache.org/jira/browse/HDFS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko closed HDFS-2064. - Warm HA NameNode going Hot -- Key: HDFS-2064

[jira] [Resolved] (HDFS-2064) Warm HA NameNode going Hot

[ https://issues.apache.org/jira/browse/HDFS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-2064. --- Resolution: Won't Fix Closing this in favor of HDFS-6469. Warm HA NameNode going

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14021017#comment-14021017 ] Konstantin Shvachko commented on HDFS-6469: --- Suresh, your questions are right to

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14021021#comment-14021021 ] Konstantin Shvachko commented on HDFS-6469: --- Lohit, you are right this phrase

[jira] [Commented] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027179#comment-14027179 ] Konstantin Shvachko commented on HDFS-6469: --- h4. Coordinated reads The

[jira] [Comment Edited] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027179#comment-14027179 ] Konstantin Shvachko edited comment on HDFS-6469 at 6/10/14 11:04 PM:

[jira] [Comment Edited] (HDFS-6469) Coordinated replication of the namespace using ConsensusNode

[ https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027179#comment-14027179 ] Konstantin Shvachko edited comment on HDFS-6469 at 6/11/14 12:32 AM:

[jira] [Commented] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259961#comment-13259961 ] Konstantin Shvachko commented on HDFS-2246: --- +1 the patch looks good. Passes all

[jira] [Updated] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-2246: -- Fix Version/s: 0.22.1 Committed to branch 0.22.1. Thanks Benoy for porting.

  1   2   3   4   5   6   7   8   9   10   >