[jira] [Created] (HDDS-1046) TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked

Shashikant Banerjee created HDDS-1046: - Summary: TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked Key: HDDS-1046 URL: https://issues.apache.org/jira/browse/HDDS-1046

[jira] [Commented] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759709#comment-16759709 ] Shashikant Banerjee commented on HDDS-935: -- Patch v4 fixes the test failures and checkstyle

[jira] [Updated] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-935: - Attachment: HDDS-935.004.patch > Avoid creating an already created container on a datanode

[jira] [Updated] (HDDS-1037) Fix the block discard logic in Ozone client

[ https://issues.apache.org/jira/browse/HDDS-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1037: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~msingh] for

[jira] [Commented] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758402#comment-16758402 ] Shashikant Banerjee commented on HDDS-935: -- Patch v3 replaces thhe Object Streams with generic

[jira] [Updated] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-935: - Attachment: HDDS-935.003.patch > Avoid creating an already created container on a datanode

[jira] [Updated] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1021: -- Attachment: HDDS-1021.001.patch > Add functionality to make a datanode participate in a

[jira] [Updated] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1021: -- Status: Open (was: Patch Available) > Add functionality to make a datanode participate

[jira] [Updated] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1021: -- Status: Patch Available (was: Open) > Add functionality to make a datanode participate

[jira] [Updated] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1021: -- Attachment: (was: HDDS-1021.001.patch) > Add functionality to make a datanode

[jira] [Commented] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

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

[jira] [Updated] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1021: -- Attachment: HDDS-1021.001.patch > Add functionality to make a datanode participate in a

[jira] [Commented] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758144#comment-16758144 ] Shashikant Banerjee commented on HDDS-935: -- patch v2: Rebased patch v1. > Avoid creating an

[jira] [Updated] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-935: - Attachment: HDDS-935.002.patch > Avoid creating an already created container on a datanode

[jira] [Commented] (HDDS-972) Add support for configuring multiple OMs

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

[jira] [Updated] (HDDS-1026) Reads should fail over to alternate replica

[ https://issues.apache.org/jira/browse/HDDS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1026: -- Attachment: HDDS-1026.001.patch > Reads should fail over to alternate replica >

[jira] [Updated] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1021: -- Status: Patch Available (was: Open) > Add functionality to make a datanode participate

[jira] [Updated] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1021: -- Attachment: HDDS-1021.000.patch > Add functionality to make a datanode participate in a

[jira] [Updated] (HDDS-1037) Fix the block discard logic in Ozone client

[ https://issues.apache.org/jira/browse/HDDS-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1037: -- Attachment: HDDS-1037.000.patch > Fix the block discard logic in Ozone client >

[jira] [Updated] (HDDS-1037) Fix the block discard logic in Ozone client

[ https://issues.apache.org/jira/browse/HDDS-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1037: -- Status: Patch Available (was: Open) > Fix the block discard logic in Ozone client >

[jira] [Created] (HDDS-1037) Fix the block discard logic in Ozone client

Shashikant Banerjee created HDDS-1037: - Summary: Fix the block discard logic in Ozone client Key: HDDS-1037 URL: https://issues.apache.org/jira/browse/HDDS-1037 Project: Hadoop Distributed Data

[jira] [Updated] (HDDS-1026) Reads should fail over to alternate replica

[ https://issues.apache.org/jira/browse/HDDS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1026: -- Attachment: HDDS-1026.000.patch > Reads should fail over to alternate replica >

[jira] [Updated] (HDDS-1026) Reads should fail over to alternate replica

[ https://issues.apache.org/jira/browse/HDDS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1026: -- Status: Patch Available (was: Open) > Reads should fail over to alternate replica >

[jira] [Assigned] (HDDS-1026) Reads should fail over to alternate replica

[ https://issues.apache.org/jira/browse/HDDS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1026: - Assignee: Shashikant Banerjee > Reads should fail over to alternate replica >

[jira] [Updated] (HDDS-1004) SCMContainerManager#updateContainerStateInternal fails for QUASI_CLOSE and FORCE_CLOSE events

[ https://issues.apache.org/jira/browse/HDDS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1004: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~ljain] for

[jira] [Created] (HDDS-1021) Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline

Shashikant Banerjee created HDDS-1021: - Summary: Add functionality to make a datanode participate in a single node Ratis as well as 3 node Ratis pipeline Key: HDDS-1021 URL:

[jira] [Created] (HDDS-1020) Client should inform SCM of a corrupt replica in case it detects one while doing a read operation

Shashikant Banerjee created HDDS-1020: - Summary: Client should inform SCM of a corrupt replica in case it detects one while doing a read operation Key: HDDS-1020 URL:

[jira] [Commented] (HDDS-1004) SCMContainerManager#updateContainerStateInternal fails for QUASI_CLOSE and FORCE_CLOSE events

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

[jira] [Commented] (HDDS-997) Add blockade Tests for scm isolation and mixed node isolation

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

[jira] [Updated] (HDDS-996) Incorrect data length gets updated in OM by client in case it hits exception in multiple successive block writes

[ https://issues.apache.org/jira/browse/HDDS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-996: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~jnp] and

[jira] [Updated] (HDDS-998) Remove XceiverClinetSpi Interface in Ozone

[ https://issues.apache.org/jira/browse/HDDS-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-998: - Description: Currently, Ratis client and StandAlone client implement the XceiverClientSpi

[jira] [Created] (HDDS-998) Remove XceiverClinetSpi Interface in Ozone

Shashikant Banerjee created HDDS-998: Summary: Remove XceiverClinetSpi Interface in Ozone Key: HDDS-998 URL: https://issues.apache.org/jira/browse/HDDS-998 Project: Hadoop Distributed Data Store

[jira] [Commented] (HDDS-981) Block allocation should involve pipeline selection and then container selection

[ https://issues.apache.org/jira/browse/HDDS-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750068#comment-16750068 ] Shashikant Banerjee commented on HDDS-981: -- Thanks [~ljain] for working on this. The patch overall

[jira] [Updated] (HDDS-996) Incorrect data length gets updated in OM by client in case it hits exception in multiple successive block writes

[ https://issues.apache.org/jira/browse/HDDS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-996: - Status: Patch Available (was: Open) > Incorrect data length gets updated in OM by client

[jira] [Updated] (HDDS-996) Incorrect data length gets updated in OM by client in case it hits exception in multiple successive block writes

[ https://issues.apache.org/jira/browse/HDDS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-996: - Attachment: HDDS-996.000.patch > Incorrect data length gets updated in OM by client in

[jira] [Created] (HDDS-996) Incorrect data length gets updated in OM by client in case it hits exception in multiple successive block writes

Shashikant Banerjee created HDDS-996: Summary: Incorrect data length gets updated in OM by client in case it hits exception in multiple successive block writes Key: HDDS-996 URL:

[jira] [Updated] (HDDS-932) Add blockade Tests for Network partition

[ https://issues.apache.org/jira/browse/HDDS-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-932: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~nilotpalnandi]

[jira] [Updated] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-935: - Attachment: HDDS-935.001.patch > Avoid creating an already created container on a datanode

[jira] [Commented] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

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

[jira] [Updated] (HDDS-913) Ozonefs defaultFs example is wrong in the documentation

[ https://issues.apache.org/jira/browse/HDDS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-913: - Status: Patch Available (was: Open) > Ozonefs defaultFs example is wrong in the

[jira] [Assigned] (HDDS-913) Ozonefs defaultFs example is wrong in the documentation

[ https://issues.apache.org/jira/browse/HDDS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-913: Assignee: Supratim Deka > Ozonefs defaultFs example is wrong in the documentation >

[jira] [Assigned] (HDDS-988) containers remain in CLOSING state in one of the datanodes when there datanodes are isolated in docker cluster

[ https://issues.apache.org/jira/browse/HDDS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-988: Assignee: Shashikant Banerjee > containers remain in CLOSING state in one of the

[jira] [Commented] (HDDS-947) Implement OzoneManager State Machine

[ https://issues.apache.org/jira/browse/HDDS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740024#comment-16740024 ] Shashikant Banerjee commented on HDDS-947: -- Thanks [~hanishakoneru] for updating the patch. +1.

[jira] [Commented] (HDDS-959) KeyOutputStream should handle retry failures

[ https://issues.apache.org/jira/browse/HDDS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739279#comment-16739279 ] Shashikant Banerjee commented on HDDS-959: -- Thanks [~ljain]. The patch does not apply to trunk

[jira] [Comment Edited] (HDDS-959) KeyOutputStream should handle retry failures

[ https://issues.apache.org/jira/browse/HDDS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739279#comment-16739279 ] Shashikant Banerjee edited comment on HDDS-959 at 1/10/19 10:31 AM:

[jira] [Commented] (HDDS-932) Add blockade Tests for Network partition

[ https://issues.apache.org/jira/browse/HDDS-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739276#comment-16739276 ] Shashikant Banerjee commented on HDDS-932: -- Thanks [~nilotpalnandi] for the patch. The patch looks

[jira] [Commented] (HDDS-947) Implement OzoneManager State Machine

[ https://issues.apache.org/jira/browse/HDDS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737994#comment-16737994 ] Shashikant Banerjee commented on HDDS-947: -- Thanks [~hanishakoneru] for updating the patch. The

[jira] [Commented] (HDDS-941) Rename ChunkGroupInputStream to keyInputStream and ChunkInputStream to BlockInputStream

[ https://issues.apache.org/jira/browse/HDDS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737862#comment-16737862 ] Shashikant Banerjee commented on HDDS-941: -- Thanks [~bharatviswa] for the review. I have addressed

[jira] [Updated] (HDDS-941) Rename ChunkGroupInputStream to keyInputStream and ChunkInputStream to BlockInputStream

[ https://issues.apache.org/jira/browse/HDDS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-941: - Attachment: HDDS-941.001.patch > Rename ChunkGroupInputStream to keyInputStream and

[jira] [Updated] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-935: - Status: Patch Available (was: Open) > Avoid creating an already created container on a

[jira] [Updated] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

[ https://issues.apache.org/jira/browse/HDDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-935: - Attachment: HDDS-935.000.patch > Avoid creating an already created container on a datanode

[jira] [Commented] (HDDS-947) Implement OzoneManager State Machine

[ https://issues.apache.org/jira/browse/HDDS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736800#comment-16736800 ] Shashikant Banerjee commented on HDDS-947: -- Thanks [~hanishakoneru] for updating the patch. The

[jira] [Updated] (HDDS-941) Rename ChunkGroupInputStream to keyInputStream and ChunkInputStream to BlockInputStream

[ https://issues.apache.org/jira/browse/HDDS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-941: - Attachment: HDDS-941.000.patch > Rename ChunkGroupInputStream to keyInputStream and

[jira] [Updated] (HDDS-941) Rename ChunkGroupInputStream to keyInputStream and ChunkInputStream to BlockInputStream

[ https://issues.apache.org/jira/browse/HDDS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-941: - Status: Patch Available (was: Open) > Rename ChunkGroupInputStream to keyInputStream and

[jira] [Commented] (HDDS-953) put key operation throws exception when run via ozone sh cli

[ https://issues.apache.org/jira/browse/HDDS-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735648#comment-16735648 ] Shashikant Banerjee commented on HDDS-953: -- This is a possible case currently , where a writeChunk

[jira] [Assigned] (HDDS-953) put key operation throws exception when run via ozone sh cli

[ https://issues.apache.org/jira/browse/HDDS-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-953: Assignee: Shashikant Banerjee > put key operation throws exception when run via

[jira] [Created] (HDDS-966) Rename ChunkGroupInputStream to KeyInputStream and ChunkInputStream to BlockInputStream

Shashikant Banerjee created HDDS-966: Summary: Rename ChunkGroupInputStream to KeyInputStream and ChunkInputStream to BlockInputStream Key: HDDS-966 URL: https://issues.apache.org/jira/browse/HDDS-966

[jira] [Commented] (HDDS-959) KeyOutputStream should handle retry failures

[ https://issues.apache.org/jira/browse/HDDS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735586#comment-16735586 ] Shashikant Banerjee commented on HDDS-959: -- Thanks [~ljain] for the patch. The patch looks good

[jira] [Comment Edited] (HDDS-959) KeyOutputStream should handle retry failures

[ https://issues.apache.org/jira/browse/HDDS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735586#comment-16735586 ] Shashikant Banerjee edited comment on HDDS-959 at 1/7/19 8:55 AM: -- Thanks

[jira] [Commented] (HDDS-934) freon run hung and did not terminate when run on non-functional pipeline

[ https://issues.apache.org/jira/browse/HDDS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725587#comment-16725587 ] Shashikant Banerjee commented on HDDS-934: -- Thanks [~nandakumar131] for the patch and

[jira] [Assigned] (HDDS-934) freon run hung and did not terminate when run on non-functional pipeline

[ https://issues.apache.org/jira/browse/HDDS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-934: Assignee: Nanda kumar (was: Shashikant Banerjee) > freon run hung and did not

[jira] [Created] (HDDS-941) Rename ChunkGroupInputStream to keyInputStream and ChunkInputStream to BlockInputStream

Shashikant Banerjee created HDDS-941: Summary: Rename ChunkGroupInputStream to keyInputStream and ChunkInputStream to BlockInputStream Key: HDDS-941 URL: https://issues.apache.org/jira/browse/HDDS-941

[jira] [Commented] (HDDS-934) freon run hung and did not terminate when run on non-functional pipeline

[ https://issues.apache.org/jira/browse/HDDS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724312#comment-16724312 ] Shashikant Banerjee commented on HDDS-934: -- Freon waits for the progress bar thread to complete

[jira] [Assigned] (HDDS-934) freon run hung and did not terminate when run on non-functional pipeline

[ https://issues.apache.org/jira/browse/HDDS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-934: Assignee: Shashikant Banerjee > freon run hung and did not terminate when run on

[jira] [Commented] (HDDS-912) Update ozone to latest ratis snapshot build (0.4.0-3b0be02-SNAPSHOT)

[ https://issues.apache.org/jira/browse/HDDS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724019#comment-16724019 ] Shashikant Banerjee commented on HDDS-912: -- Thanks [~ljain] for updating the patch. The test

[jira] [Updated] (HDDS-912) Update ozone to latest ratis snapshot build (0.4.0-3b0be02-SNAPSHOT)

[ https://issues.apache.org/jira/browse/HDDS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-912: - Resolution: Fixed Fix Version/s: 0.4.0 Status: Resolved (was: Patch

[jira] [Updated] (HDDS-925) Rename ChunkGroupOutputStream to KeyOutputStream and ChunkOutputStream to BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-925: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~msingh] for

[jira] [Created] (HDDS-935) Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart

Shashikant Banerjee created HDDS-935: Summary: Avoid creating an already created container on a datanode in case of disk removal followed by datanode restart Key: HDDS-935 URL:

[jira] [Commented] (HDDS-912) Update ozone to latest ratis snapshot build (0.4.0-3b0be02-SNAPSHOT)

[ https://issues.apache.org/jira/browse/HDDS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723951#comment-16723951 ] Shashikant Banerjee commented on HDDS-912: -- Thanks [~ljain] for the patch. The patch looks good to

[jira] [Updated] (HDDS-539) Ozone datanode command ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-539: - Resolution: Fixed Fix Version/s: 0.4.0 Status: Resolved (was: Patch

[jira] [Assigned] (HDDS-539) Ozone datanode command ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-539: Assignee: Shashikant Banerjee (was: Vinicius Higa Murakami) > Ozone datanode

[jira] [Assigned] (HDDS-539) Ozone datanode command ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-539: Assignee: Vinicius Higa Murakami (was: Shashikant Banerjee) > Ozone datanode

[jira] [Updated] (HDDS-539) Ozone datanode command ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-539: - Summary: Ozone datanode command ignores the invalid options (was: Ozone datanode ignores

[jira] [Updated] (HDDS-539) Ozone datanode ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-539: - Summary: Ozone datanode ignores the invalid options (was: ozone datanode ignores the

[jira] [Commented] (HDDS-539) ozone datanode ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723912#comment-16723912 ] Shashikant Banerjee commented on HDDS-539: -- Thanks [~vmurakami] for updating the patch. The patch

[jira] [Commented] (HDDS-539) ozone datanode ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722686#comment-16722686 ] Shashikant Banerjee commented on HDDS-539: -- Thanks [~vmurakami] for updating the patch. Some tests

[jira] [Commented] (HDDS-539) ozone datanode ignores the invalid options

[ https://issues.apache.org/jira/browse/HDDS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720352#comment-16720352 ] Shashikant Banerjee commented on HDDS-539: -- Thanks [~vmurakami] for the patch. The patch looks

[jira] [Updated] (HDDS-925) Rename ChunkGroupOutputStream to KeyOutputStream and ChunkOutputStream to BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-925: - Attachment: HDDS-925.000.patch > Rename ChunkGroupOutputStream to KeyOutputStream and

[jira] [Updated] (HDDS-925) Rename ChunkGroupOutputStream to KeyOutputStream and ChunkOutputStream to BlockOutputStream

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

[jira] [Created] (HDDS-925) Rename ChunkGroupOutputStream to KeyOutputStream and ChunkOutputStream to BlockOutputStream

Shashikant Banerjee created HDDS-925: Summary: Rename ChunkGroupOutputStream to KeyOutputStream and ChunkOutputStream to BlockOutputStream Key: HDDS-925 URL: https://issues.apache.org/jira/browse/HDDS-925

[jira] [Commented] (HDDS-871) XceiverClientRatis#watchForCommit closes raft client at every call

[ https://issues.apache.org/jira/browse/HDDS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713495#comment-16713495 ] Shashikant Banerjee commented on HDDS-871: -- This will be fixed as a part of HDDS-870. >

[jira] [Commented] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711802#comment-16711802 ] Shashikant Banerjee commented on HDDS-870: -- Test Failures reported are not related to the patch.

[jira] [Commented] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711691#comment-16711691 ] Shashikant Banerjee commented on HDDS-870: -- Patch v9 address the test failure related to 

[jira] [Updated] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-870: - Attachment: HDDS-870.009.patch > Avoid creating block sized buffer in

[jira] [Commented] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711261#comment-16711261 ] Shashikant Banerjee commented on HDDS-870: -- Thanks [~jnp] for the review comments. patch v8

[jira] [Updated] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-870: - Attachment: HDDS-870.008.patch > Avoid creating block sized buffer in

[jira] [Updated] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-890: - Attachment: HDDS-890.000.patch > Handle OverlappingFileLockException during

[jira] [Updated] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-890: - Component/s: Ozone Datanode > Handle OverlappingFileLockException during

[jira] [Updated] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-890: - Affects Version/s: 0.4.0 > Handle OverlappingFileLockException during

[jira] [Updated] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-890: - Description: With raft log entries getting truncated, the corresponding

[jira] [Updated] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-890: - Description: With raft log entries getting truncated, the corresponding

[jira] [Updated] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-890: - Description: With raft log entries getting truncated, the corresponding

[jira] [Assigned] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-890: Assignee: Shashikant Banerjee > Handle OverlappingFileLockException during

[jira] [Created] (HDDS-890) Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine

Shashikant Banerjee created HDDS-890: Summary: Handle OverlappingFileLockException during writeStateMachineData in ContainerStateMachine Key: HDDS-890 URL: https://issues.apache.org/jira/browse/HDDS-890

[jira] [Commented] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706077#comment-16706077 ] Shashikant Banerjee commented on HDDS-870: -- Thanks [~msingh] for the review comments.  {code:java}

[jira] [Updated] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-870: - Attachment: (was: HDDS-870.004.patch) > Avoid creating block sized buffer in

[jira] [Updated] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-870: - Attachment: HDDS-870.004.patch > Avoid creating block sized buffer in

[jira] [Updated] (HDDS-870) Avoid creating block sized buffer in ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-870: - Attachment: HDDS-870.004.patch > Avoid creating block sized buffer in

[jira] [Updated] (HDDS-882) Provide a config to optionally turn on/off the sync flag during chunk writes

[ https://issues.apache.org/jira/browse/HDDS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-882: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~jnp] for the

[jira] [Commented] (HDDS-887) Add DispatcherContext info to Dispatcher from containerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706064#comment-16706064 ] Shashikant Banerjee commented on HDDS-887: -- Thanks [~jnp] for the review. The checkstyle issues

<    3   4   5   6   7   8   9   10   11   12   >