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

[ https://issues.apache.org/jira/browse/HDDS-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-966. -- Resolution: Fixed > Rename ChunkGroupInputStream to KeyInputStream and ChunkInputStream

[jira] [Assigned] (HDDS-372) There are three buffer copies in BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-372: Assignee: Shashikant Banerjee (was: Tsz Wo Nicholas Sze) > There are three buffer

[jira] [Updated] (HDDS-372) There are three buffer copies in BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-372: - Description: Currently, there are three buffer copies in ChunkOutputStream # from byte[]

[jira] [Updated] (HDDS-372) There are three buffer copies in BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-372: - Description: Currently, there are two buffer copies in ChunkOutputStream # from byte[] to

[jira] [Updated] (HDDS-372) There are three buffer copies in BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-372: - Summary: There are three buffer copies in BlockOutputStream (was: There are two buffer

[jira] [Work stopped] (HDDS-372) There are three buffer copies in BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDDS-372 stopped by Shashikant Banerjee. > There are three buffer copies in BlockOutputStream >

[jira] [Updated] (HDDS-1184) Parallelization of write chunks in datanodes is broken

[ https://issues.apache.org/jira/browse/HDDS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1184: -- Attachment: HDDS-1184.000.patch > Parallelization of write chunks in datanodes is

[jira] [Updated] (HDDS-1184) Parallelization of write chunks in datanodes is broken

[ https://issues.apache.org/jira/browse/HDDS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1184: -- Status: Patch Available (was: Open) > Parallelization of write chunks in datanodes is

[jira] [Updated] (HDDS-1184) Parallelization of write chunks in datanodes is broken

[ https://issues.apache.org/jira/browse/HDDS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1184: -- Description: After the HDDS-4 branch merge, parallelization in write chunks and

[jira] [Created] (HDDS-1184) Parallelization of write chunks in datanodes is broken

Shashikant Banerjee created HDDS-1184: - Summary: Parallelization of write chunks in datanodes is broken Key: HDDS-1184 URL: https://issues.apache.org/jira/browse/HDDS-1184 Project: Hadoop

[jira] [Commented] (HDDS-1088) Add blockade Tests to test Replica Manager

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

[jira] [Resolved] (HDDS-1124) java.lang.IllegalStateException exception in datanode log

[ https://issues.apache.org/jira/browse/HDDS-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-1124. --- Resolution: Not A Problem Fix Version/s: 0.5.0 >

[jira] [Resolved] (HDDS-1125) java.lang.InterruptedException seen in datanode logs

[ https://issues.apache.org/jira/browse/HDDS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-1125. --- Resolution: Not A Problem Fix Version/s: 0.4.0 >

[jira] [Commented] (HDDS-451) PutKey failed due to error "Rejecting write chunk request. Chunk overwrite without explicit request"

[ https://issues.apache.org/jira/browse/HDDS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16779032#comment-16779032 ] Shashikant Banerjee commented on HDDS-451: -- We have not been able to reproduce this issue anymore.

[jira] [Resolved] (HDDS-582) Remove ChunkOutputStreamEntry class from ChunkGroupOutputStream

[ https://issues.apache.org/jira/browse/HDDS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-582. -- Resolution: Won't Do Fix Version/s: 0.5.0 > Remove ChunkOutputStreamEntry class

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16778020#comment-16778020 ] Shashikant Banerjee commented on HDDS-726: -- Rebased patch v8 > Ozone Client should update SCM to

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.008.patch > Ozone Client should update SCM to move the container out

[jira] [Comment Edited] (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=16777923#comment-16777923 ] Shashikant Banerjee edited comment on HDDS-935 at 2/26/19 1:47 PM: ---

[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=16777923#comment-16777923 ] Shashikant Banerjee commented on HDDS-935: -- Thanks [~arpitagarwal] for the review. Patch v6

[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.006.patch > Avoid creating an already created container on a datanode

[jira] [Updated] (HDDS-1174) Freon tests are failing with null pointer exception

[ https://issues.apache.org/jira/browse/HDDS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1174: -- Description: java.lang.NullPointerException at

[jira] [Updated] (HDDS-1174) Freon tests are failing with null pointer exception

[ https://issues.apache.org/jira/browse/HDDS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1174: -- Attachment: HDDS-1174.000.patch > Freon tests are failing with null pointer exception >

[jira] [Updated] (HDDS-1174) Freon tests are failing with null pointer exception

[ https://issues.apache.org/jira/browse/HDDS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1174: -- Attachment: HDDS-1174.001.patch > Freon tests are failing with null pointer exception >

[jira] [Updated] (HDDS-1174) Freon tests are failing with null pointer exception

[ https://issues.apache.org/jira/browse/HDDS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1174: -- Attachment: (was: HDDS-1174.000.patch) > Freon tests are failing with null pointer

[jira] [Updated] (HDDS-1174) Freon tests are failing with null pointer exception

[ https://issues.apache.org/jira/browse/HDDS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1174: -- Status: Open (was: Patch Available) > Freon tests are failing with null pointer

[jira] [Updated] (HDDS-1174) Freon tests are failing with null pointer exception

[ https://issues.apache.org/jira/browse/HDDS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1174: -- Status: Patch Available (was: Open) > Freon tests are failing with null pointer

[jira] [Updated] (HDDS-1174) Freon tests are failing with null pointer exception

[ https://issues.apache.org/jira/browse/HDDS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1174: -- Environment: {code:java}  {code} was: {code:java} java.lang.NullPointerException at

[jira] [Commented] (HDDS-1173) Fix a data corruption bug in BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776807#comment-16776807 ] Shashikant Banerjee commented on HDDS-1173: --- Patch vo is dependent on HDDS-726. > Fix a data

[jira] [Updated] (HDDS-1173) Fix a data corruption bug in BlockOutputStream

[ https://issues.apache.org/jira/browse/HDDS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1173: -- Attachment: HDDS-1173.000.patch > Fix a data corruption bug in BlockOutputStream >

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776805#comment-16776805 ] Shashikant Banerjee commented on HDDS-726: -- Patch v7 fixes  checkstyle, findbug and related test

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.007.patch > Ozone Client should update SCM to move the container out

[jira] [Created] (HDDS-1174) Freon tests are failing with null pointer exception

Shashikant Banerjee created HDDS-1174: - Summary: Freon tests are failing with null pointer exception Key: HDDS-1174 URL: https://issues.apache.org/jira/browse/HDDS-1174 Project: Hadoop Distributed

[jira] [Created] (HDDS-1173) Fix a data corruption bug in BlockOutputStream

Shashikant Banerjee created HDDS-1173: - Summary: Fix a data corruption bug in BlockOutputStream Key: HDDS-1173 URL: https://issues.apache.org/jira/browse/HDDS-1173 Project: Hadoop Distributed Data

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776518#comment-16776518 ] Shashikant Banerjee commented on HDDS-726: --  Patch v6 is rebased. > Ozone Client should update

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.006.patch > Ozone Client should update SCM to move the container out

[jira] [Commented] (HDDS-1152) Add trace information for the client side of the datanode writes

[ https://issues.apache.org/jira/browse/HDDS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774747#comment-16774747 ] Shashikant Banerjee commented on HDDS-1152: --- +1. Looks good to me. > Add trace information for

[jira] [Commented] (HDDS-1152) Add trace information for the client side of the datanode writes

[ https://issues.apache.org/jira/browse/HDDS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774020#comment-16774020 ] Shashikant Banerjee commented on HDDS-1152: --- Thanks[~elek] for the patch. I think  {code:java}

[jira] [Commented] (HDDS-1151) Propagate the tracing id in ScmBlockLocationProtocol

[ https://issues.apache.org/jira/browse/HDDS-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774006#comment-16774006 ] Shashikant Banerjee commented on HDDS-1151: --- The patch looks good to me. +1 .Pending jenkins >

[jira] [Updated] (HDDS-1120) Add a config to disable checksum verification during read even though checksum data is present in the persisted data

[ https://issues.apache.org/jira/browse/HDDS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1120: -- Status: Open (was: Patch Available) > Add a config to disable checksum verification

[jira] [Created] (HDDS-1144) Introduce an option to optionally save the ratis log data when thhe pipeline gets destroyed

Shashikant Banerjee created HDDS-1144: - Summary: Introduce an option to optionally save the ratis log data when thhe pipeline gets destroyed Key: HDDS-1144 URL: https://issues.apache.org/jira/browse/HDDS-1144

[jira] [Created] (HDDS-1143) Ensure stateMachineData to be evicted only after writeStateMachineData completes in ContainerStateMachine cache

Shashikant Banerjee created HDDS-1143: - Summary: Ensure stateMachineData to be evicted only after writeStateMachineData completes in ContainerStateMachine cache Key: HDDS-1143 URL:

[jira] [Commented] (HDDS-1125) java.lang.InterruptedException seen in datanode logs

[ https://issues.apache.org/jira/browse/HDDS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773033#comment-16773033 ] Shashikant Banerjee commented on HDDS-1125: --- There is gc pauses in the leader, because of which

[jira] [Commented] (HDDS-1124) java.lang.IllegalStateException exception in datanode log

[ https://issues.apache.org/jira/browse/HDDS-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773027#comment-16773027 ] Shashikant Banerjee commented on HDDS-1124: --- 172.27.76.72 being a leader sends append request to

[jira] [Created] (HDDS-1142) Inconsistency in Ozone log rollovers

Shashikant Banerjee created HDDS-1142: - Summary: Inconsistency in Ozone log rollovers Key: HDDS-1142 URL: https://issues.apache.org/jira/browse/HDDS-1142 Project: Hadoop Distributed Data Store

[jira] [Assigned] (HDDS-1124) java.lang.IllegalStateException exception in datanode log

[ https://issues.apache.org/jira/browse/HDDS-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1124: - Assignee: Shashikant Banerjee > java.lang.IllegalStateException exception in

[jira] [Commented] (HDDS-1095) OzoneManager#openKey should do multiple block allocations in a single SCM rpc call

[ https://issues.apache.org/jira/browse/HDDS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772802#comment-16772802 ] Shashikant Banerjee commented on HDDS-1095: --- [~msingh],Thanks for updating the patch. I have two

[jira] [Comment Edited] (HDDS-1095) OzoneManager#openKey should do multiple block allocations in a single SCM rpc call

[ https://issues.apache.org/jira/browse/HDDS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772802#comment-16772802 ] Shashikant Banerjee edited comment on HDDS-1095 at 2/20/19 9:20 AM:

[jira] [Commented] (HDDS-1086) Remove RaftClient from OM

[ https://issues.apache.org/jira/browse/HDDS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772597#comment-16772597 ] Shashikant Banerjee commented on HDDS-1086: --- Thanks [~hanishakoneru]. In the case mentioned, we

[jira] [Created] (HDDS-1135) Ozone jars are missing in the Ozone Snapshot tar

Shashikant Banerjee created HDDS-1135: - Summary: Ozone jars are missing in the Ozone Snapshot tar Key: HDDS-1135 URL: https://issues.apache.org/jira/browse/HDDS-1135 Project: Hadoop Distributed

[jira] [Assigned] (HDDS-1125) java.lang.InterruptedException seen in datanode logs

[ https://issues.apache.org/jira/browse/HDDS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1125: - Assignee: Shashikant Banerjee > java.lang.InterruptedException seen in datanode

[jira] [Commented] (HDDS-1086) Remove RaftClient from OM

[ https://issues.apache.org/jira/browse/HDDS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771589#comment-16771589 ] Shashikant Banerjee commented on HDDS-1086: --- Thanks [~hanishakoneru] for reporting this. I have

[jira] [Commented] (HDDS-1098) Introduce Retry Policy in Ozone Client

[ https://issues.apache.org/jira/browse/HDDS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771318#comment-16771318 ] Shashikant Banerjee commented on HDDS-1098: --- Patch v0 is dependent on HDDS-726. > Introduce

[jira] [Updated] (HDDS-1098) Introduce Retry Policy in Ozone Client

[ https://issues.apache.org/jira/browse/HDDS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1098: -- Attachment: HDDS-1098.000.patch > Introduce Retry Policy in Ozone Client >

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.005.patch > Ozone Client should update SCM to move the container out

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

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

[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] [Comment Edited] (HDDS-1121) Key read failure when data is written parallel in to Ozone

[ https://issues.apache.org/jira/browse/HDDS-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770986#comment-16770986 ] Shashikant Banerjee edited comment on HDDS-1121 at 2/18/19 10:44 AM: -

[jira] [Commented] (HDDS-1121) Key read failure when data is written parallel in to Ozone

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

[jira] [Commented] (HDDS-1121) Key read failure when data is written parallel in to Ozone

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

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770775#comment-16770775 ] Shashikant Banerjee commented on HDDS-726: -- Thanks [~msingh]. Patch v4 is rebased. > Ozone Client

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.004.patch > Ozone Client should update SCM to move the container out

[jira] [Updated] (HDDS-1120) Add a config to disable checksum verification during read even though checksum data is present in the persisted data

[ https://issues.apache.org/jira/browse/HDDS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1120: -- Summary: Add a config to disable checksum verification during read even though checksum

[jira] [Created] (HDDS-1120) Add a config to disable checksum verification during read if though checksum data is present in the persisted data

Shashikant Banerjee created HDDS-1120: - Summary: Add a config to disable checksum verification during read if though checksum data is present in the persisted data Key: HDDS-1120 URL:

[jira] [Updated] (HDDS-1076) TestSCMNodeManager crashed the jvm

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

[jira] [Commented] (HDDS-1082) OutOfMemoryError because of memory leak in KeyInputStream

[ https://issues.apache.org/jira/browse/HDDS-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769424#comment-16769424 ] Shashikant Banerjee commented on HDDS-1082: --- The 100 GB key write/read has been successfully

[jira] [Commented] (HDDS-1076) TestSCMNodeManager crashed the jvm

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

[jira] [Updated] (HDDS-1028) Improve logging in SCMPipelineManager

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

[jira] [Commented] (HDDS-1082) OutOfMemoryError while reading key of size 100GB

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

[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=16768212#comment-16768212 ] Shashikant Banerjee commented on HDDS-935: -- Thanks [~msingh] for the review and offline

[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.005.patch > Avoid creating an already created container on a datanode

[jira] [Commented] (HDDS-1076) TestSCMNodeManager crashed the jvm

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

[jira] [Commented] (HDDS-1028) Improve logging in SCMPipelineManager

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

[jira] [Updated] (HDDS-1096) OzoneManager#loadOMHAConfigs should use default ports in case port is not defined

[ https://issues.apache.org/jira/browse/HDDS-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1096: -- Status: Patch Available (was: Open) > OzoneManager#loadOMHAConfigs should use default

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

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

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.003.patch > Ozone Client should update SCM to move the container out

[jira] [Created] (HDDS-1098) Introduce Retry Policy in Ozone Client

Shashikant Banerjee created HDDS-1098: - Summary: Introduce Retry Policy in Ozone Client Key: HDDS-1098 URL: https://issues.apache.org/jira/browse/HDDS-1098 Project: Hadoop Distributed Data Store

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767456#comment-16767456 ] Shashikant Banerjee commented on HDDS-726: -- Patch v2 : added some more tests and fixed the test

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.002.patch > Ozone Client should update SCM to move the container out

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.001.patch > Ozone Client should update SCM to move the container out

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Status: Patch Available (was: Open) > Ozone Client should update SCM to move the

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: (was: HDDS-726.001.patch) > Ozone Client should update SCM to move the

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Status: Open (was: Patch Available) > Ozone Client should update SCM to move the

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.001.patch > Ozone Client should update SCM to move the container out

[jira] [Commented] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766340#comment-16766340 ] Shashikant Banerjee commented on HDDS-726: -- 1st patch V0 updated. Will add more tests in the next

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Status: Patch Available (was: Open) > Ozone Client should update SCM to move the

[jira] [Updated] (HDDS-726) Ozone Client should update SCM to move the container out of allocation path in case a write transaction fails

[ https://issues.apache.org/jira/browse/HDDS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-726: - Attachment: HDDS-726.000.patch > Ozone Client should update SCM to move the container out

[jira] [Assigned] (HDDS-1067) freon run on client gets hung when two of the datanodes are down in 3 datanode cluster

[ https://issues.apache.org/jira/browse/HDDS-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1067: - Assignee: Shashikant Banerjee > freon run on client gets hung when two of the

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

[ https://issues.apache.org/jira/browse/HDDS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764300#comment-16764300 ] Shashikant Banerjee edited comment on HDDS-1026 at 2/10/19 5:30 AM:

[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: -- Resolution: Fixed Fix Version/s: 0.4.0 Status: Resolved (was: Patch

[jira] [Commented] (HDDS-1057) get key operation fails when client cannot communicate with 2 of the datanodes in 3 node cluster

[ https://issues.apache.org/jira/browse/HDDS-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762733#comment-16762733 ] Shashikant Banerjee commented on HDDS-1057: --- The key seems be allocated on a single node Ratis 

[jira] [Assigned] (HDDS-1057) get key operation fails when client cannot communicate with 2 of the datanodes in 3 node cluster

[ https://issues.apache.org/jira/browse/HDDS-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1057: - Assignee: Shashikant Banerjee > get key operation fails when client cannot

[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=16761696#comment-16761696 ] Shashikant Banerjee commented on HDDS-972: -- Thanks [~hanishakoneru] for updating the patch. The

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

[ https://issues.apache.org/jira/browse/HDDS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761575#comment-16761575 ] Shashikant Banerjee commented on HDDS-1026: --- rebased patch v2. > Reads should fail over to

[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.002.patch > Reads should fail over to alternate replica >

[jira] [Resolved] (HDDS-1051) TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked is failing

[ https://issues.apache.org/jira/browse/HDDS-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-1051. --- Resolution: Duplicate >

[jira] [Updated] (HDDS-1046) TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked fails intermittently

[ https://issues.apache.org/jira/browse/HDDS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1046: -- Labels: newbie (was: ) >

[jira] [Commented] (HDDS-1046) TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked fails intermittently

[ https://issues.apache.org/jira/browse/HDDS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760084#comment-16760084 ] Shashikant Banerjee commented on HDDS-1046: --- The test needs to be fixed here as, in the test

[jira] [Commented] (HDDS-1046) TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked fails intermittently

[ https://issues.apache.org/jira/browse/HDDS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759806#comment-16759806 ] Shashikant Banerjee commented on HDDS-1046: --- SCM logs clearly show that , the container is in

[jira] [Updated] (HDDS-1046) TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked fails intermittently

[ https://issues.apache.org/jira/browse/HDDS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1046: -- Summary: TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked fails

[jira] [Updated] (HDDS-1046) TestCloseContainerByPipeline#testIfCloseContainerCommandHandlerIsInvoked fails intermittently

[ https://issues.apache.org/jira/browse/HDDS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1046: -- Description:   {code:java} java.lang.StackOverflowError at

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