[jira] [Created] (HDDS-2146) Optimize block write path performance by reducing no of watchForCommit calls

Shashikant Banerjee created HDDS-2146: - Summary: Optimize block write path performance by reducing no of watchForCommit calls Key: HDDS-2146 URL: https://issues.apache.org/jira/browse/HDDS-2146

[jira] [Created] (HDDS-2145) Optimize client read path by reading multiple chunks along with block info in a single rpc call.

Shashikant Banerjee created HDDS-2145: - Summary: Optimize client read path by reading multiple chunks along with block info in a single rpc call. Key: HDDS-2145 URL:

[jira] [Commented] (HDDS-2132) TestKeyValueContainer is failing

[ https://issues.apache.org/jira/browse/HDDS-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931609#comment-16931609 ] Shashikant Banerjee commented on HDDS-2132: --- Until and unless, a putBlock command gets executed

[jira] [Updated] (HDDS-2132) TestKeyValueContainer is failing

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

[jira] [Updated] (HDDS-1786) Datanodes takeSnapshot should delete previously created snapshots

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

[jira] [Updated] (HDDS-2117) ContainerStateMachine#writeStateMachineData times out

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

[jira] [Created] (HDDS-2117) ContainerStateMachine#writeStateMachineData times out

Shashikant Banerjee created HDDS-2117: - Summary: ContainerStateMachine#writeStateMachineData times out Key: HDDS-2117 URL: https://issues.apache.org/jira/browse/HDDS-2117 Project: Hadoop

[jira] [Updated] (HDFS-13660) DistCp job fails when new data is appended in the file while the distCp copy job is running

[ https://issues.apache.org/jira/browse/HDFS-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13660: --- Status: Patch Available (was: Open) > DistCp job fails when new data is appended in

[jira] [Updated] (HDDS-2032) Ozone client should retry writes in case of any ratis/stateMachine exceptions

[ https://issues.apache.org/jira/browse/HDDS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2032: -- Status: Patch Available (was: Open) > Ozone client should retry writes in case of any

[jira] [Updated] (HDDS-1843) Undetectable corruption after restart of a datanode

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

[jira] [Updated] (HDDS-2076) Read fails because the block cannot be located in the container

[ https://issues.apache.org/jira/browse/HDDS-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2076: -- Status: Patch Available (was: Open) > Read fails because the block cannot be located

[jira] [Commented] (HDDS-2076) Read fails because the block cannot be located in the container

[ https://issues.apache.org/jira/browse/HDDS-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921441#comment-16921441 ] Shashikant Banerjee commented on HDDS-2076: --- >From the OM logs , container 7 exists on the

[jira] [Updated] (HDDS-1783) Latency metric for applyTransaction in ContainerStateMachine

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

[jira] [Assigned] (HDDS-2076) Read fails because the block cannot be located in the container

[ https://issues.apache.org/jira/browse/HDDS-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-2076: - Assignee: Shashikant Banerjee > Read fails because the block cannot be located

[jira] [Resolved] (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 resolved HDDS-953. -- Resolution: Duplicate > put key operation throws exception when run via ozone sh cli >

[jira] [Resolved] (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 resolved HDDS-988. -- Fix Version/s: 0.5.0 Resolution: Cannot Reproduce This is not reproducible

[jira] [Assigned] (HDDS-1806) Handle writeStateMachine Failures in Ozone

[ https://issues.apache.org/jira/browse/HDDS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1806: - Assignee: Supratim Deka (was: Shashikant Banerjee) > Handle writeStateMachine

[jira] [Updated] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1843: -- Status: Patch Available (was: Open) > Undetectable corruption after restart of a

[jira] [Updated] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1843: -- Status: Open (was: Patch Available) > Undetectable corruption after restart of a

[jira] [Commented] (HDDS-2056) Datanode unable to start command handler thread with security enabled

[ https://issues.apache.org/jira/browse/HDDS-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918463#comment-16918463 ] Shashikant Banerjee commented on HDDS-2056: --- cc [~xyao] > Datanode unable to start command

[jira] [Created] (HDDS-2056) Datanode unable to start command handler thread with security enabled

Shashikant Banerjee created HDDS-2056: - Summary: Datanode unable to start command handler thread with security enabled Key: HDDS-2056 URL: https://issues.apache.org/jira/browse/HDDS-2056 Project:

[jira] [Resolved] (HDDS-720) ContainerReportPublisher fails when the container is marked unhealthy on Datanodes

[ https://issues.apache.org/jira/browse/HDDS-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-720. -- Fix Version/s: 0.5.0 Resolution: Duplicate > ContainerReportPublisher fails when

[jira] [Updated] (HDDS-2037) Fix hadoop version in pom.ozone.xml

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

[jira] [Updated] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1843: -- Status: Patch Available (was: Open) > Undetectable corruption after restart of a

[jira] [Updated] (HDDS-1753) Datanode unable to find chunk while replication data using ratis.

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

[jira] [Comment Edited] (HDDS-1610) applyTransaction failure should not be lost on restart

[ https://issues.apache.org/jira/browse/HDDS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916913#comment-16916913 ] Shashikant Banerjee edited comment on HDDS-1610 at 8/27/19 5:59 PM:

[jira] [Commented] (HDDS-1610) applyTransaction failure should not be lost on restart

[ https://issues.apache.org/jira/browse/HDDS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916913#comment-16916913 ] Shashikant Banerjee commented on HDDS-1610: --- Let me file a Jira to fix this. > applyTransaction

[jira] [Commented] (HDDS-1610) applyTransaction failure should not be lost on restart

[ https://issues.apache.org/jira/browse/HDDS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916912#comment-16916912 ] Shashikant Banerjee commented on HDDS-1610: --- [~boky01], yes it was unintended. Thanks for

[jira] [Commented] (HDDS-2043) "VOLUME_NOT_FOUND" exception thrown while listing volumes

[ https://issues.apache.org/jira/browse/HDDS-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916906#comment-16916906 ] Shashikant Banerjee commented on HDDS-2043: --- Here is the output of ozone version: {code:java}

[jira] [Updated] (HDDS-2043) "VOLUME_NOT_FOUND" exception thrown while listing volumes

[ https://issues.apache.org/jira/browse/HDDS-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2043: -- Fix Version/s: 0.4.1 > "VOLUME_NOT_FOUND" exception thrown while listing volumes >

[jira] [Updated] (HDDS-2043) "VOLUME_NOT_FOUND" exception thrown while listing volumes

[ https://issues.apache.org/jira/browse/HDDS-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2043: -- Priority: Blocker (was: Major) > "VOLUME_NOT_FOUND" exception thrown while listing

[jira] [Commented] (HDDS-2043) "VOLUME_NOT_FOUND" exception thrown while listing volumes

[ https://issues.apache.org/jira/browse/HDDS-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916896#comment-16916896 ] Shashikant Banerjee commented on HDDS-2043: --- Restarting OM fixes the issue. Looks like a bug in

[jira] [Updated] (HDDS-1998) TestSecureContainerServer#testClientServerRatisGrpc is failing

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

[jira] [Updated] (HDDS-1998) TestSecureContainerServer#testClientServerRatisGrpc is failing

[ https://issues.apache.org/jira/browse/HDDS-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1998: -- Fix Version/s: 0.5.0 > TestSecureContainerServer#testClientServerRatisGrpc is failing >

[jira] [Updated] (HDDS-2032) Ozone client should retry writes in case of any ratis/stateMachine exceptions

[ https://issues.apache.org/jira/browse/HDDS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2032: -- Description: Currently, Ozone client retry writes on a different pipeline or container

[jira] [Updated] (HDDS-2032) Ozone client should retry writes in case of any ratis/stateMachine exceptions

[ https://issues.apache.org/jira/browse/HDDS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2032: -- Summary: Ozone client should retry writes in case of any ratis/stateMachine exceptions

[jira] [Created] (HDDS-2032) Ozone client retry writes in case of any ratis/stateMachine exceptions

Shashikant Banerjee created HDDS-2032: - Summary: Ozone client retry writes in case of any ratis/stateMachine exceptions Key: HDDS-2032 URL: https://issues.apache.org/jira/browse/HDDS-2032

[jira] [Updated] (HDDS-1753) Datanode unable to find chunk while replication data using ratis.

[ https://issues.apache.org/jira/browse/HDDS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1753: -- Status: Patch Available (was: Open) > Datanode unable to find chunk while replication

[jira] [Assigned] (HDDS-1890) Add metrics for data pipeline performance monitoring in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1890: - Assignee: Supratim Deka (was: Shashikant Banerjee) > Add metrics for data

[jira] [Updated] (HDDS-1610) applyTransaction failure should not be lost on restart

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

[jira] [Commented] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908897#comment-16908897 ] Shashikant Banerjee commented on HDFS-13101: Thanks

[jira] [Commented] (HDDS-1753) Datanode unable to find chunk while replication data using ratis.

[ https://issues.apache.org/jira/browse/HDDS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908895#comment-16908895 ] Shashikant Banerjee commented on HDDS-1753: --- Uploaded patch v0 to address the issue. The patch

[jira] [Updated] (HDDS-1753) Datanode unable to find chunk while replication data using ratis.

[ https://issues.apache.org/jira/browse/HDDS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1753: -- Attachment: HDDS-1753.000.patch > Datanode unable to find chunk while replication data

[jira] [Updated] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1836: -- Resolution: Won't Do Status: Resolved (was: Patch Available) > Change the

[jira] [Updated] (HDDS-1908) TestMultiBlockWritesWithDnFailures is failing

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

[jira] [Commented] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903853#comment-16903853 ] Shashikant Banerjee commented on HDFS-13101: Thanks [~szetszwo] for the review. Patch v4

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Attachment: HDFS-13101.004.patch > Yet another fsimage corruption related to

[jira] [Comment Edited] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901067#comment-16901067 ] Shashikant Banerjee edited comment on HDDS-1843 at 8/6/19 1:39 PM: ---

[jira] [Issue Comment Deleted] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1843: -- Comment: was deleted (was: Added an initial patch v0 to address the problem. The patch

[jira] [Commented] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901067#comment-16901067 ] Shashikant Banerjee commented on HDDS-1843: --- Added an innitial patch v0 to address the problem.

[jira] [Commented] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901068#comment-16901068 ] Shashikant Banerjee commented on HDDS-1843: --- Added an initial patch v0 to address the problem.

[jira] [Updated] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1843: -- Attachment: HDDS-1843.000.patch > Undetectable corruption after restart of a datanode >

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Attachment: HDFS-13101.003.patch > Yet another fsimage corruption related to

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Status: Patch Available (was: Open) > Yet another fsimage corruption related to

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Status: Open (was: Patch Available) > Yet another fsimage corruption related to

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Attachment: (was: HDFS-13101.003.patch) > Yet another fsimage corruption related

[jira] [Comment Edited] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900253#comment-16900253 ] Shashikant Banerjee edited comment on HDFS-13101 at 8/5/19 5:21 PM:

[jira] [Commented] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900253#comment-16900253 ] Shashikant Banerjee commented on HDFS-13101: Thanks [~szetszwo] [~jojochuang] [~smeng] for

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Attachment: HDFS-13101.003.patch > Yet another fsimage corruption related to

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Status: Patch Available (was: Open) > Yet another fsimage corruption related to

[jira] [Assigned] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1843: - Assignee: Shashikant Banerjee (was: Hrishikesh Gadre) > Undetectable corruption

[jira] [Updated] (HDDS-1798) Propagate failure in writeStateMachineData to Ratis

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

[jira] [Commented] (HDDS-1739) Handle Apply Transaction Failure in State Machine

[ https://issues.apache.org/jira/browse/HDDS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899058#comment-16899058 ] Shashikant Banerjee commented on HDDS-1739: --- [~sdeka], steps 1-3 are added as part of HDDS-1610.

[jira] [Updated] (HDDS-1878) checkstyle error in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1878: -- Fix Version/s: 0.5.0 > checkstyle error in ContainerStateMachine >

[jira] [Updated] (HDDS-1832) Improve logging for PipelineActions handling in SCM and datanode

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

[jira] [Updated] (HDDS-1878) checkstyle error in ContainerStateMachine

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

[jira] [Updated] (HDDS-1782) Add an option to MiniOzoneChaosCluster to read files multiple times.

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

[jira] [Created] (HDDS-1890) Add metrics for data pipeline performance monitoring in ContainerStateMachine

Shashikant Banerjee created HDDS-1890: - Summary: Add metrics for data pipeline performance monitoring in ContainerStateMachine Key: HDDS-1890 URL: https://issues.apache.org/jira/browse/HDDS-1890

[jira] [Assigned] (HDDS-1753) Datanode unable to find chunk while replication data using ratis.

[ https://issues.apache.org/jira/browse/HDDS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1753: - Assignee: Shashikant Banerjee (was: Lokesh Jain) > Datanode unable to find

[jira] [Commented] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897982#comment-16897982 ] Shashikant Banerjee commented on HDFS-13101: Thanks [~jojochuang] for simplifying the test

[jira] [Updated] (HDDS-1816) ContainerStateMachine should limit number of pending apply transactions

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

[jira] [Comment Edited] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896814#comment-16896814 ] Shashikant Banerjee edited comment on HDFS-13101 at 7/31/19 6:44 AM: -

[jira] [Commented] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896814#comment-16896814 ] Shashikant Banerjee commented on HDFS-13101: Attached a patch containing a test case which

[jira] [Updated] (HDFS-13101) Yet another fsimage corruption related to snapshot

[ https://issues.apache.org/jira/browse/HDFS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDFS-13101: --- Attachment: HDFS-13101.corruption_repro.patch > Yet another fsimage corruption

[jira] [Updated] (HDDS-1864) Turn on topology aware read in TestFailureHandlingByClient

[ https://issues.apache.org/jira/browse/HDDS-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1864: -- Resolution: Fixed Fix Version/s: 0.5.0 Target Version/s: 0.5.0

[jira] [Created] (HDDS-1869) Turn on Network Topology related configs for MiniOzoneChaosCluster

Shashikant Banerjee created HDDS-1869: - Summary: Turn on Network Topology related configs for MiniOzoneChaosCluster Key: HDDS-1869 URL: https://issues.apache.org/jira/browse/HDDS-1869 Project:

[jira] [Updated] (HDDS-1749) Ozone Client should randomize the list of nodes in pipeline for reads

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

[jira] [Updated] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1843: -- Description: Right now, all write chunks use BufferedIO ie, sync flag is disabled by

[jira] [Commented] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892429#comment-16892429 ] Shashikant Banerjee commented on HDDS-1843: --- The solution to address the problem here is as

[jira] [Updated] (HDDS-1843) Undetectable corruption after restart of a datanode

[ https://issues.apache.org/jira/browse/HDDS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1843: -- Summary: Undetectable corruption after restart of a datanode (was: Close container

[jira] [Comment Edited] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890636#comment-16890636 ] Shashikant Banerjee edited comment on HDDS-1836 at 7/23/19 4:06 AM:

[jira] [Comment Edited] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890636#comment-16890636 ] Shashikant Banerjee edited comment on HDDS-1836 at 7/23/19 3:02 AM:

[jira] [Comment Edited] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890636#comment-16890636 ] Shashikant Banerjee edited comment on HDDS-1836 at 7/23/19 3:01 AM:

[jira] [Comment Edited] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890636#comment-16890636 ] Shashikant Banerjee edited comment on HDDS-1836 at 7/23/19 3:01 AM:

[jira] [Commented] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890636#comment-16890636 ] Shashikant Banerjee commented on HDDS-1836: --- [~arp], in test environment, with a limited set of

[jira] [Created] (HDDS-1844) Tune the stateMachineDataCache to a reasonable fraction of Datanode Heap

Shashikant Banerjee created HDDS-1844: - Summary: Tune the stateMachineDataCache to a reasonable fraction of Datanode Heap Key: HDDS-1844 URL: https://issues.apache.org/jira/browse/HDDS-1844

[jira] [Created] (HDDS-1843) Close container command should sync the Rocks db before changing to closed state.

Shashikant Banerjee created HDDS-1843: - Summary: Close container command should sync the Rocks db before changing to closed state. Key: HDDS-1843 URL: https://issues.apache.org/jira/browse/HDDS-1843

[jira] [Comment Edited] (HDDS-1753) Datanode unable to find chunk while replication data using ratis.

[ https://issues.apache.org/jira/browse/HDDS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883727#comment-16883727 ] Shashikant Banerjee edited comment on HDDS-1753 at 7/22/19 3:06 PM:

[jira] [Updated] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1836: -- Status: Patch Available (was: Open) > Change the default value of ratis leader

[jira] [Updated] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

[ https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1836: -- Description: The default value of min leader election timeout currently is 5s(done with

[jira] [Created] (HDDS-1836) Change the default value of ratis leader election min timeout to a lower value

Shashikant Banerjee created HDDS-1836: - Summary: Change the default value of ratis leader election min timeout to a lower value Key: HDDS-1836 URL: https://issues.apache.org/jira/browse/HDDS-1836

[jira] [Updated] (HDDS-1779) TestWatchForCommit tests are flaky

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

[jira] [Updated] (HDDS-1654) Ensure container state on datanode gets synced to disk whenever state change happens

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

[jira] [Updated] (HDDS-1780) TestFailureHandlingByClient tests are flaky

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

[jira] [Resolved] (HDDS-1821) BlockOutputStream#watchForCommit fails with UnsupportedOperationException when one DN is down

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

[jira] [Resolved] (HDDS-1789) BlockOutputStream#watchForCommit fails with UnsupportedOperationException

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

[jira] [Updated] (HDDS-1492) Generated chunk size name too long.

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

[jira] [Assigned] (HDDS-1809) Ozone Read fails with StatusRunTimeExceptions after 2 datanode fail in Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-1809: - Assignee: Sammi Chen > Ozone Read fails with StatusRunTimeExceptions after 2

[jira] [Updated] (HDDS-1809) Ozone Read fails with StatusRunTimeExceptions after 2 datanode fail in Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1809: -- Component/s: Ozone Client > Ozone Read fails with StatusRunTimeExceptions after 2

[jira] [Updated] (HDDS-1809) Ozone Read fails with StatusRunTimeExceptions after 2 datanode fail in Ratis pipeline

[ https://issues.apache.org/jira/browse/HDDS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1809: -- Component/s: (was: Ozone Client) > Ozone Read fails with StatusRunTimeExceptions

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