[jira] [Updated] (HDDS-383) Ozone Client should cache closed container Info to discard preallocated blocks from closed containers

[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Summary: Ozone Client should cache closed container Info to discard preallocated blocks

[jira] [Created] (HDDS-383) Ozone Client should closed container Info to discard preallocated blocks from closed containers

Shashikant Banerjee created HDDS-383: Summary: Ozone Client should closed container Info to discard preallocated blocks from closed containers Key: HDDS-383 URL: https://issues.apache.org/jira/browse/HDDS-383

[jira] [Commented] (HDFS-13860) Space character in the path is shown as "+" while creating dirs in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595237#comment-16595237 ] Shashikant Banerjee commented on HDFS-13860: The fix breaks the compatiblity. Cancelling the

[jira] [Updated] (HDFS-13860) Space character in the path is shown as "+" while creating dirs in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13860: --- Status: Open (was: Patch Available) > Space character in the path is shown as "+"

[jira] [Updated] (HDFS-13860) Space character in the path is shown as "+" while creating dirs in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13860: --- Summary: Space character in the path is shown as "+" while creating dirs in WebHDFS

[jira] [Updated] (HDFS-13860) Space character in the filePath is shown as "+" while creating dirs in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13860: --- Summary: Space character in the filePath is shown as "+" while creating dirs in

[jira] [Updated] (HDFS-13860) Space character in the filePath is shown as "+" while creating files in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13860: --- Attachment: HDFS-13860.00.patch > Space character in the filePath is shown as "+"

[jira] [Updated] (HDFS-13860) Space character in the filePath is shown as "+" while creating files in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13860: --- Status: Patch Available (was: Open) > Space character in the filePath is shown as

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Attachment: (was: HDDS-263.02.patch) > Add retries in Ozone Client to handle

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Attachment: HDDS-263.02.patch > Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED

[jira] [Commented] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594593#comment-16594593 ] Shashikant Banerjee commented on HDDS-263: -- Patch v2 fixes most of the checkstyle issues. > Add

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Attachment: HDDS-263.02.patch > Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED

[jira] [Updated] (HDDS-380) Remove synchronization from ChunkGroupOutputStream and ChunkOutputStream

[ https://issues.apache.org/jira/browse/HDDS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-380: - Fix Version/s: (was: 0.3.0) 0.2.1 > Remove synchronization from

[jira] [Commented] (HDDS-365) Implement flushStateMachineData for containerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594551#comment-16594551 ] Shashikant Banerjee commented on HDDS-365: -- Thanks [~msingh] for the review. patch v1 addresses

[jira] [Updated] (HDDS-365) Implement flushStateMachineData for containerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-365: - Attachment: HDDS-365.01.patch > Implement flushStateMachineData for containerStateMachine

[jira] [Updated] (HDDS-380) Remove synchronization from ChunkGroupOutputStream and ChunkOutputStream

[ https://issues.apache.org/jira/browse/HDDS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-380: - Attachment: HDDS-380.00.patch > Remove synchronization from ChunkGroupOutputStream and

[jira] [Updated] (HDDS-380) Remove synchronization from ChunkGroupOutputStream and ChunkOutputStream

[ https://issues.apache.org/jira/browse/HDDS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-380: - Status: Patch Available (was: Open) > Remove synchronization from ChunkGroupOutputStream

[jira] [Created] (HDDS-380) Remove synchronization from ChunkGroupOutputStream and ChunkOutputStream

Shashikant Banerjee created HDDS-380: Summary: Remove synchronization from ChunkGroupOutputStream and ChunkOutputStream Key: HDDS-380 URL: https://issues.apache.org/jira/browse/HDDS-380 Project:

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Description: While Ozone client writes are going on, a container on a datanode can gets

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Status: Patch Available (was: Open) > Add retries in Ozone Client to handle

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Attachment: HDDS-263.01.patch > Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Status: Open (was: Patch Available) > Add retries in Ozone Client to handle

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Attachment: (was: HDDS-263.01.patch) > Add retries in Ozone Client to handle

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Status: Patch Available (was: Open) > Add retries in Ozone Client to handle

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Attachment: HDDS-263.01.patch > Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593967#comment-16593967 ] Shashikant Banerjee commented on HDDS-247: -- Rebased to latest trunk > Handle CLOSED_CONTAINER_IO

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.13.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Updated] (HDDS-365) Implement flushStateMachineData for containerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-365: - Status: Patch Available (was: Open) > Implement flushStateMachineData for

[jira] [Updated] (HDDS-365) Implement flushStateMachineData for containerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-365: - Attachment: HDDS-365.00.patch > Implement flushStateMachineData for containerStateMachine

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593534#comment-16593534 ] Shashikant Banerjee commented on HDDS-247: -- Thanks [~nandakumar131], for the review comments.

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.12.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592540#comment-16592540 ] Shashikant Banerjee commented on HDDS-247: -- Thanks [~msingh], for the review .patch v11 addresses

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.11.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591647#comment-16591647 ] Shashikant Banerjee commented on HDDS-247: -- Thanks [~msingh], [~szetszwo], for the review

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: (was: HDDS-247.10.patch) > Handle CLOSED_CONTAINER_IO exception in

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.10.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.10.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Created] (HDDS-371) Add RetriableException class in Ozone

Shashikant Banerjee created HDDS-371: Summary: Add RetriableException class in Ozone Key: HDDS-371 URL: https://issues.apache.org/jira/browse/HDDS-371 Project: Hadoop Distributed Data Store

[jira] [Assigned] (HDFS-13860) Space character in the filePath is shown as "+" while creating files in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDFS-13860: -- Assignee: Shashikant Banerjee > Space character in the filePath is shown as

[jira] [Updated] (HDFS-13860) Space character in the filePath is shown as "+" while creating files in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13860: --- Summary: Space character in the filePath is shown as "+" while creating files in

[jira] [Updated] (HDFS-13860) Space character in the filePath is encode as "+" while creating files in WebHDFS

[ https://issues.apache.org/jira/browse/HDFS-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13860: --- Description: $ ./hdfs dfs -mkdir webhdfs://127.0.0.1/tmp1/"file 1" 2018-08-23

[jira] [Created] (HDFS-13860) Space character in the filePath is encode as "+" while creating files in WebHDFS

Shashikant Banerjee created HDFS-13860: -- Summary: Space character in the filePath is encode as "+" while creating files in WebHDFS Key: HDFS-13860 URL: https://issues.apache.org/jira/browse/HDFS-13860

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588611#comment-16588611 ] Shashikant Banerjee commented on HDDS-247: -- Patch v9 fixes the findbugs, checkstyle and unit test

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.09.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587938#comment-16587938 ] Shashikant Banerjee commented on HDDS-247: -- Thanks [~nandakumar131], for the review comments. As

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.08.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16585669#comment-16585669 ] Shashikant Banerjee commented on HDDS-247: -- Rebased patch v6. > Handle CLOSED_CONTAINER_IO

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.07.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Created] (HDDS-365) Implement flushStateMachineData for containerStateMachine

Shashikant Banerjee created HDDS-365: Summary: Implement flushStateMachineData for containerStateMachine Key: HDDS-365 URL: https://issues.apache.org/jira/browse/HDDS-365 Project: Hadoop

[jira] [Resolved] (HDDS-244) Synchronize PutKey and WriteChunk requests in Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-244. -- Resolution: Fixed > Synchronize PutKey and WriteChunk requests in Ratis Server >

[jira] [Commented] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16582446#comment-16582446 ] Shashikant Banerjee commented on HDDS-179: -- Patch v12 fixes the checkstyle issues. Test failures

[jira] [Created] (HDDS-353) Multiple delete Blocks tests are failing consistetly

Shashikant Banerjee created HDDS-353: Summary: Multiple delete Blocks tests are failing consistetly Key: HDDS-353 URL: https://issues.apache.org/jira/browse/HDDS-353 Project: Hadoop Distributed

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-179: - Attachment: HDDS-179.12.patch > CloseContainer command should be executed only if all the

[jira] [Commented] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16582195#comment-16582195 ] Shashikant Banerjee commented on HDDS-179: -- Thanks [~msingh] for the review comments. Patch

[jira] [Comment Edited] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16582195#comment-16582195 ] Shashikant Banerjee edited comment on HDDS-179 at 8/16/18 8:35 AM: ---

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-179: - Attachment: HDDS-179.11.patch > CloseContainer command should be executed only if all the

[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579452#comment-16579452 ] Shashikant Banerjee commented on HDDS-247: -- Patch v6 is rebased. > Handle CLOSED_CONTAINER_IO

[jira] [Updated] (HDDS-247) Handle CLOSED_CONTAINER_IO exception in ozoneClient

[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-247: - Attachment: HDDS-247.06.patch > Handle CLOSED_CONTAINER_IO exception in ozoneClient >

[jira] [Resolved] (HDDS-295) TestCloseContainerByPipeline is failing because of timeout

[ https://issues.apache.org/jira/browse/HDDS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-295. -- Resolution: Duplicate Fix Version/s: 0.2.1 > TestCloseContainerByPipeline is

[jira] [Commented] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578713#comment-16578713 ] Shashikant Banerjee commented on HDDS-179: -- Patch v10 adds some more detailed comments for

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-179: - Attachment: HDDS-179.10.patch > CloseContainer command should be executed only if all the

[jira] [Commented] (HDDS-333) Create an Ozone Logo

[ https://issues.apache.org/jira/browse/HDDS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578689#comment-16578689 ] Shashikant Banerjee commented on HDDS-333: -- +1, 4th logo. > Create an Ozone Logo >

[jira] [Commented] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578204#comment-16578204 ] Shashikant Banerjee commented on HDDS-179: -- Test failures and asflicense warnings are not related

[jira] [Commented] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578042#comment-16578042 ] Shashikant Banerjee commented on HDDS-179: -- As per offline discussion with [~msingh], patch v9 is

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-179: - Attachment: HDDS-179.09,patch > CloseContainer command should be executed only if all the

[jira] [Commented] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576194#comment-16576194 ] Shashikant Banerjee commented on HDDS-179: -- Thanks [~ljain], for the review comments. As per

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-179: - Status: Patch Available (was: Open) > CloseContainer command should be executed only if

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-179: - Attachment: HDDS-179.08.patch > CloseContainer command should be executed only if all the

[jira] [Comment Edited] (HDDS-324) Use pipeline name as Ratis groupID to allow datanode to report pipeline info

[ https://issues.apache.org/jira/browse/HDDS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575977#comment-16575977 ] Shashikant Banerjee edited comment on HDDS-324 at 8/10/18 9:01 AM: ---

[jira] [Commented] (HDDS-324) Use pipeline name as Ratis groupID to allow datanode to report pipeline info

[ https://issues.apache.org/jira/browse/HDDS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575977#comment-16575977 ] Shashikant Banerjee commented on HDDS-324: -- Thanks [~msingh], for working on this. The patch looks

[jira] [Resolved] (HDDS-322) Restructure ChunkGroupOutputStream and ChunkOutputStream

[ https://issues.apache.org/jira/browse/HDDS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-322. -- Resolution: Won't Do > Restructure ChunkGroupOutputStream and ChunkOutputStream >

[jira] [Commented] (HDFS-13816) dfs.getQuotaUsage() throws NPE on non-existent dir instead of FileNotFoundException

[ https://issues.apache.org/jira/browse/HDFS-13816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575937#comment-16575937 ] Shashikant Banerjee commented on HDFS-13816: Thanks [~vinayrpet] for reporting and working on

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Attachment: HDDS-327.03.patch > CloseContainer command handler in HDDS Dispatcher should

[jira] [Commented] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575332#comment-16575332 ] Shashikant Banerjee commented on HDDS-327: -- Thanks [~hanishakoneru], fir the review. Patch v3

[jira] [Commented] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575037#comment-16575037 ] Shashikant Banerjee commented on HDDS-327: -- As per offline discussion with [~hanishakoneru],

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Attachment: HDDS-327.02.patch > CloseContainer command handler in HDDS Dispatcher should

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Attachment: (was: HDDS-327.02.patch) > CloseContainer command handler in HDDS

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Attachment: HDDS-327.02.patch > CloseContainer command handler in HDDS Dispatcher should

[jira] [Resolved] (HDDS-86) Add functionality in Node2CotainerMap to list missing open containers

[ https://issues.apache.org/jira/browse/HDDS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-86. - Resolution: Won't Do > Add functionality in Node2CotainerMap to list missing open

[jira] [Updated] (HDDS-132) Update SCMNodeStorageStatMap while processing Node Report

[ https://issues.apache.org/jira/browse/HDDS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-132: - Fix Version/s: (was: 0.2.1) 0.3.0 > Update SCMNodeStorageStatMap

[jira] [Commented] (HDFS-13809) NPE in DataNode#getDiskBalancerStatus() when the DN is restarted

[ https://issues.apache.org/jira/browse/HDFS-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574636#comment-16574636 ] Shashikant Banerjee commented on HDFS-13809: +1 > NPE in DataNode#getDiskBalancerStatus()

[jira] [Updated] (HDDS-306) Add functionality to construct OpenContainerBlockMap on datanode restart

[ https://issues.apache.org/jira/browse/HDDS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-306: - Fix Version/s: (was: 0.2.1) 0.3.0 > Add functionality to construct

[jira] [Commented] (HDDS-333) Create an Ozone Logo

[ https://issues.apache.org/jira/browse/HDDS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574520#comment-16574520 ] Shashikant Banerjee commented on HDDS-333: -- +1 > Create an Ozone Logo > > >

[jira] [Commented] (HDDS-339) Add block length and blockId in PutKeyResponse

[ https://issues.apache.org/jira/browse/HDDS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574517#comment-16574517 ] Shashikant Banerjee commented on HDDS-339: -- Thanks [~msingh], for the review comments. Patch v1

[jira] [Updated] (HDDS-339) Add block length and blockId in PutKeyResponse

[ https://issues.apache.org/jira/browse/HDDS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-339: - Attachment: HDDS-339.01.patch > Add block length and blockId in PutKeyResponse >

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Attachment: (was: HDDS-327.02.patch) > CloseContainer command handler in HDDS

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Attachment: HDDS-327.02.patch > CloseContainer command handler in HDDS Dispatcher should

[jira] [Commented] (HDFS-13668) FSPermissionChecker may throws AIOOE when check if inode has permission

[ https://issues.apache.org/jira/browse/HDFS-13668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574260#comment-16574260 ] Shashikant Banerjee commented on HDFS-13668: Thanks [~hexiaoqiao], for reporting and working

[jira] [Commented] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573755#comment-16573755 ] Shashikant Banerjee commented on HDDS-263: -- Patch v0 is blocked on HDDS-247. Not submitting it for

[jira] [Updated] (HDDS-263) Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED Exception

[ https://issues.apache.org/jira/browse/HDDS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-263: - Attachment: HDDS-263.00.patch > Add retries in Ozone Client to handle BLOCK_NOT_COMMITTED

[jira] [Commented] (HDDS-339) Add block length and blockId in PutKeyResponse

[ https://issues.apache.org/jira/browse/HDDS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573482#comment-16573482 ] Shashikant Banerjee commented on HDDS-339: -- Ptach v1 adds GetCommittedBlockLength response to

[jira] [Updated] (HDDS-339) Add block length and blockId in PutKeyResponse

[ https://issues.apache.org/jira/browse/HDDS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-339: - Attachment: HDDS-339.00.patch > Add block length and blockId in PutKeyResponse >

[jira] [Updated] (HDDS-339) Add block length and blockId in PutKeyResponse

[ https://issues.apache.org/jira/browse/HDDS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-339: - Status: Patch Available (was: Open) > Add block length and blockId in PutKeyResponse >

[jira] [Resolved] (HDDS-197) DataNode should return ContainerClosingException/ContainerClosedException (CCE) to client if the container is in Closing/Closed State

[ https://issues.apache.org/jira/browse/HDDS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-197. -- Resolution: Fixed Fixed in the current code with HDDS-173. > DataNode should return

[jira] [Created] (HDDS-339) Add block length and blockId in PutKeyResponse

Shashikant Banerjee created HDDS-339: Summary: Add block length and blockId in PutKeyResponse Key: HDDS-339 URL: https://issues.apache.org/jira/browse/HDDS-339 Project: Hadoop Distributed Data

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

[ https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-179: - Status: Open (was: Patch Available) > CloseContainer command should be executed only if

[jira] [Commented] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571667#comment-16571667 ] Shashikant Banerjee commented on HDDS-327: -- Patch v1 adds the handling of container in Closing

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Status: Patch Available (was: Open) > CloseContainer command handler in HDDS Dispatcher

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Attachment: HDDS-327.01.patch > CloseContainer command handler in HDDS Dispatcher should

[jira] [Updated] (HDDS-327) CloseContainer command handler in HDDS Dispatcher should not throw exception if the container is already closed

[ https://issues.apache.org/jira/browse/HDDS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-327: - Status: Open (was: Patch Available) > CloseContainer command handler in HDDS Dispatcher

<    9   10   11   12   13   14   15   16   17   18   >