[jira] [Updated] (HDDS-3764) Spark is failing with no such method exception

[ https://issues.apache.org/jira/browse/HDDS-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marton Elek updated HDDS-3764: -- Summary: Spark is failing with no such method exception (was: Spark is failiing with no such method exc

[jira] [Updated] (HDDS-2284) XceiverClientMetrics should be initialised as part of XceiverClientManager constructor

[ https://issues.apache.org/jira/browse/HDDS-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2284: -- Target Version/s: 0.7.0 (was: 0.6.0) > XceiverClientMetrics should be initialised as pa

[jira] [Updated] (HDDS-1206) Handle Datanode volume out of space

[ https://issues.apache.org/jira/browse/HDDS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1206: -- Target Version/s: 0.7.0 (was: 0.6.0) > Handle Datanode volume out of space > --

[jira] [Updated] (HDDS-1286) Add more unit tests to validate exception path during write for Ozone client

[ https://issues.apache.org/jira/browse/HDDS-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1286: -- Target Version/s: 0.7.0 (was: 0.6.0) > Add more unit tests to validate exception path d

[jira] [Updated] (HDDS-800) Avoid ByteString to byte array conversion cost by using ByteBuffer

[ https://issues.apache.org/jira/browse/HDDS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-800: - Target Version/s: 0.7.0 (was: 0.6.0) > Avoid ByteString to byte array conversion cost by u

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

[ https://issues.apache.org/jira/browse/HDDS-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-371. -- Fix Version/s: 0.6.0 Resolution: Won't Do > Add RetriableException class in Ozone

[jira] [Resolved] (HDDS-986) Stack overflow in TestFailureHandlingByClient

[ https://issues.apache.org/jira/browse/HDDS-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-986. -- Fix Version/s: 0.6.0 Resolution: Cannot Reproduce > Stack overflow in TestFailureH

[jira] [Resolved] (HDDS-1438) TestOzoneClientRetriesOnException#testGroupMismatchExceptionHandling is failing because of allocate block failures

[ https://issues.apache.org/jira/browse/HDDS-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-1438. --- Fix Version/s: 0.6.0 Resolution: Fixed > TestOzoneClientRetriesOnException#test

[jira] [Updated] (HDDS-1325) Exception thrown while initializing ozoneClientAdapter

[ https://issues.apache.org/jira/browse/HDDS-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1325: -- Target Version/s: 0.7.0 (was: 0.6.0) > Exception thrown while initializing ozoneClientA

[jira] [Updated] (HDDS-1446) Grpc channels are leaked in XceiverClientGrpc

[ https://issues.apache.org/jira/browse/HDDS-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1446: -- Target Version/s: 0.7.0 (was: 0.6.0) > Grpc channels are leaked in XceiverClientGrpc >

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

[ https://issues.apache.org/jira/browse/HDDS-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2145: -- Labels: (was: TriagePending) > Optimize client read path by reading multiple chunks al

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

[ https://issues.apache.org/jira/browse/HDDS-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2145: -- Target Version/s: 0.7.0 (was: 0.6.0) > Optimize client read path by reading multiple ch

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

[ https://issues.apache.org/jira/browse/HDDS-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2146: -- Target Version/s: 0.7.0 (was: 0.6.0) > Optimize block write path performance by reducin

[GitHub] [hadoop-ozone] timmylicheng commented on pull request #1019: HDDS-3679. Add unit tests for PipelineManagerV2.

timmylicheng commented on pull request #1019: URL: https://github.com/apache/hadoop-ozone/pull/1019#issuecomment-641767465 Dump shows it's related to rocksdb. Not sure if it's related to multiple DBs being merged. Stack looks weird to me. Any ideas? @nandakumar131 @elek @xiaoyuyao

[jira] [Resolved] (HDDS-2702) Client failed to recover from ratis AlreadyClosedException exception

[ https://issues.apache.org/jira/browse/HDDS-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-2702. --- Fix Version/s: 0.6.0 Resolution: Fixed > Client failed to recover from ratis Al

[jira] [Resolved] (HDDS-3268) CommitWatcher#watchForCommit does not timeout

[ https://issues.apache.org/jira/browse/HDDS-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-3268. --- Fix Version/s: 0.6.0 Resolution: Fixed > CommitWatcher#watchForCommit does not

[jira] [Resolved] (HDDS-2306) Fix TestWatchForCommit failure

[ https://issues.apache.org/jira/browse/HDDS-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-2306. --- Fix Version/s: 0.6.0 Resolution: Fixed > Fix TestWatchForCommit failure > -

[jira] [Resolved] (HDDS-2332) BlockOutputStream#waitOnFlushFutures blocks on putBlock combined future

[ https://issues.apache.org/jira/browse/HDDS-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-2332. --- Fix Version/s: 0.6.0 Resolution: Fixed > BlockOutputStream#waitOnFlushFutures b

[jira] [Resolved] (HDDS-2963) Use RequestDependentRetry Policy along with ExceptionDependentRetry Policy in OzoneClient

[ https://issues.apache.org/jira/browse/HDDS-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-2963. --- Fix Version/s: 0.6.0 Resolution: Fixed > Use RequestDependentRetry Policy along

[jira] [Commented] (HDDS-3611) Ozone client should not consider closed container error as failure

[ https://issues.apache.org/jira/browse/HDDS-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130117#comment-17130117 ] Lokesh Jain commented on HDDS-3611: --- [~shashikant] I am marking this back to 0.6.0. 1TB

[jira] [Updated] (HDDS-3611) Ozone client should not consider closed container error as failure

[ https://issues.apache.org/jira/browse/HDDS-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-3611: -- Target Version/s: 0.6.0 (was: 0.7.0) > Ozone client should not consider closed container error as failu

[jira] [Updated] (HDDS-2189) Datanode should send PipelineAction on RaftServer failure

[ https://issues.apache.org/jira/browse/HDDS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2189: -- Target Version/s: 0.7.0 (was: 0.6.0) > Datanode should send PipelineAction on RaftServe

[jira] [Updated] (HDDS-2342) ContainerStateMachine$chunkExecutor threads hold onto native memory

[ https://issues.apache.org/jira/browse/HDDS-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2342: -- Target Version/s: 0.7.0 (was: 0.6.0) > ContainerStateMachine$chunkExecutor threads hold

[jira] [Updated] (HDDS-2660) Create insight point for datanode container protocol

[ https://issues.apache.org/jira/browse/HDDS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2660: -- Target Version/s: 0.7.0 (was: 0.6.0) > Create insight point for datanode container prot

[jira] [Updated] (HDDS-3022) Datanode unable to close Pipeline after disk out of space

[ https://issues.apache.org/jira/browse/HDDS-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3022: -- Target Version/s: 0.7.0 (was: 0.6.0) > Datanode unable to close Pipeline after disk out

[jira] [Updated] (HDDS-2476) Share more code between metadata and data scanners

[ https://issues.apache.org/jira/browse/HDDS-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2476: -- Target Version/s: 0.7.0 (was: 0.6.0) > Share more code between metadata and data scanne

[jira] [Resolved] (HDDS-3163) write Key is hung when write delay is injected in datanode dir

[ https://issues.apache.org/jira/browse/HDDS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-3163. --- Fix Version/s: 0.6.0 Resolution: Fixed > write Key is hung when write delay is

[jira] [Updated] (HDDS-3498) Address already in use Should shutdown the datanode with FATAL log and point out the port and configure key

[ https://issues.apache.org/jira/browse/HDDS-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3498: -- Target Version/s: 0.7.0 (was: 0.6.0) > Address already in use Should shutdown the datan

[jira] [Updated] (HDDS-2696) Document recovery from RATIS-677

[ https://issues.apache.org/jira/browse/HDDS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2696: -- Target Version/s: 0.7.0 (was: 0.6.0) > Document recovery from RATIS-677 > -

[jira] [Resolved] (HDDS-3514) Fix Memory leak of RaftServerImpl

[ https://issues.apache.org/jira/browse/HDDS-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-3514. --- Fix Version/s: 0.6.0 Resolution: Fixed > Fix Memory leak of RaftServerImpl > --

[jira] [Updated] (HDDS-2701) Avoid read from temporary chunk file in datanode

[ https://issues.apache.org/jira/browse/HDDS-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-2701: -- Target Version/s: 0.7.0 (was: 0.6.0) > Avoid read from temporary chunk file in datanode

[jira] [Updated] (HDDS-1560) RejectedExecutionException on datanode after shutting it down

[ https://issues.apache.org/jira/browse/HDDS-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1560: -- Target Version/s: 0.7.0 (was: 0.6.0) > RejectedExecutionException on datanode after shu

[jira] [Updated] (HDDS-3227) Ensure eviction of stateMachineData from cache only when both followers catch up

[ https://issues.apache.org/jira/browse/HDDS-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3227: -- Fix Version/s: (was: 0.6.0) > Ensure eviction of stateMachineData from cache only wh

[jira] [Updated] (HDDS-3018) Fix TestContainerStateMachineFailures.java

[ https://issues.apache.org/jira/browse/HDDS-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3018: -- Target Version/s: 0.7.0 (was: 0.6.0) > Fix TestContainerStateMachineFailures.java > ---

[jira] [Updated] (HDDS-3227) Ensure eviction of stateMachineData from cache only when both followers catch up

[ https://issues.apache.org/jira/browse/HDDS-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3227: -- Target Version/s: 0.7.0 (was: 0.6.0) > Ensure eviction of stateMachineData from cache o

[jira] [Updated] (HDDS-3136) retry timeout is large while writing key

[ https://issues.apache.org/jira/browse/HDDS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3136: -- Parent: HDDS-3350 Issue Type: Sub-task (was: Bug) > retry timeout is large whil

[jira] [Updated] (HDDS-3594) ManagedChannels are leaked in XceiverClientGrpc manager

[ https://issues.apache.org/jira/browse/HDDS-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3594: -- Target Version/s: 0.7.0 (was: 0.6.0) > ManagedChannels are leaked in XceiverClientGrpc

[jira] [Updated] (HDDS-3600) ManagedChannels leaked on ratis pipeline when there are many connection retries

[ https://issues.apache.org/jira/browse/HDDS-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3600: -- Target Version/s: 0.7.0 (was: 0.6.0) > ManagedChannels leaked on ratis pipeline when th

[GitHub] [hadoop-ozone] Simon0806 commented on a change in pull request #1041: HDDS-3725. Ozone sh volume client support quota option

Simon0806 commented on a change in pull request #1041: URL: https://github.com/apache/hadoop-ozone/pull/1041#discussion_r437873358 ## File path: hadoop-hdds/docs/content/shell/VolumeCommands.md ## @@ -42,7 +42,7 @@ assign it to a user. | Uri | The na

[jira] [Updated] (HDDS-3611) Ozone client should not consider closed container error as failure

[ https://issues.apache.org/jira/browse/HDDS-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3611: -- Target Version/s: 0.7.0 (was: 0.6.0) > Ozone client should not consider closed containe

[jira] [Commented] (HDDS-3481) SCM ask too many datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130090#comment-17130090 ] runzhiwang commented on HDDS-3481: -- bq. Should we consider balancing the replication sour

[jira] [Updated] (HDDS-3701) Change Close container exception logging to debug in ContainerUtils#logAndReturnError

[ https://issues.apache.org/jira/browse/HDDS-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3701: -- Target Version/s: 0.7.0 (was: 0.6.0) > Change Close container exception logging to debu

[jira] [Updated] (HDDS-3702) Consider avoiding stream/map/sum in IO path

[ https://issues.apache.org/jira/browse/HDDS-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3702: -- Target Version/s: 0.7.0 (was: 0.6.0) > Consider avoiding stream/map/sum in IO path > --

[jira] [Updated] (HDDS-3559) Datanode doesn't handle java heap OutOfMemory exception

[ https://issues.apache.org/jira/browse/HDDS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3559: -- Target Version/s: 0.7.0 (was: 0.6.0) > Datanode doesn't handle java heap OutOfMemory ex

[jira] [Updated] (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 updated HDDS-1890: -- Target Version/s: 0.7.0 (was: 0.6.0) > Add metrics for data pipeline performance monito

[jira] [Updated] (HDDS-1866) Enable purging of raft logs in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1866: -- Target Version/s: 0.7.0 (was: 0.6.0) > Enable purging of raft logs in ContainerStateMac

[jira] [Updated] (HDDS-1980) Datanode should sync the db for open containers in the pipeline during stateMachine close

[ https://issues.apache.org/jira/browse/HDDS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1980: -- Target Version/s: 0.7.0 (was: 0.6.0) > Datanode should sync the db for open containers

[jira] [Updated] (HDDS-1480) Ip address should not be a part of the DatanodeID since it can change

[ https://issues.apache.org/jira/browse/HDDS-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1480: -- Target Version/s: 0.7.0 (was: 0.6.0) > Ip address should not be a part of the DatanodeI

[jira] [Updated] (HDDS-1537) TestContainerPersistence#testDeleteBlockTwice is failing

[ https://issues.apache.org/jira/browse/HDDS-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1537: -- Target Version/s: 0.7.0 (was: 0.6.0) > TestContainerPersistence#testDeleteBlockTwice is

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

[ https://issues.apache.org/jira/browse/HDDS-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1844: -- Target Version/s: 0.7.0 (was: 0.6.0) > Tune the stateMachineDataCache to a reasonable f

[jira] [Resolved] (HDDS-1408) TestMiniOzoneCluster.testDNstartAfterSCM fails with OverlappingFileLockException

[ https://issues.apache.org/jira/browse/HDDS-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-1408. --- Resolution: Implemented > TestMiniOzoneCluster.testDNstartAfterSCM fails with > Overl

[jira] [Resolved] (HDDS-1251) all chunks are not deleted by block deletion even when all keys are deleted and all containers are closed

[ https://issues.apache.org/jira/browse/HDDS-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved HDDS-1251. --- Target Version/s: 0.7.0 (was: 0.6.0) Resolution: Not A Problem It will be a

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

[ https://issues.apache.org/jira/browse/HDDS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1143: -- Target Version/s: 0.7.0 (was: 0.6.0) > Ensure stateMachineData to be evicted only after

[jira] [Updated] (HDDS-904) RATIS group not found thrown on datanodes while leader election

[ https://issues.apache.org/jira/browse/HDDS-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-904: - Target Version/s: 0.7.0 (was: 0.6.0) > RATIS group not found thrown on datanodes while lea

[jira] [Updated] (HDDS-1102) Confusing error log when datanode tries to connect to a destroyed pipeline

[ https://issues.apache.org/jira/browse/HDDS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-1102: -- Target Version/s: 0.7.0 (was: 0.6.0) > Confusing error log when datanode tries to conne

[GitHub] [hadoop-ozone] vivekratnavel commented on pull request #1047: HDDS-3726. Upload code coverage data to Codecov and enable checks in …

vivekratnavel commented on pull request #1047: URL: https://github.com/apache/hadoop-ozone/pull/1047#issuecomment-641723229 @elek @adoroszlai We will start seeing diffs in code coverage report once this patch gets merged to master. -

[jira] [Commented] (HDDS-3481) SCM ask too many datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130067#comment-17130067 ] Xiaoyu Yao commented on HDDS-3481: -- bq. The reason is source datanode replicates too many

[GitHub] [hadoop-ozone] bharatviswa504 commented on pull request #1002: HDDS-3642. Stop/Pause Background services while replacing OM DB with checkpoint from Leader

bharatviswa504 commented on pull request #1002: URL: https://github.com/apache/hadoop-ozone/pull/1002#issuecomment-641719335 Looks like it is failing in compilation and also check style issues. This is an automated message fr

[GitHub] [hadoop-ozone] bharatviswa504 commented on a change in pull request #1002: HDDS-3642. Stop/Pause Background services while replacing OM DB with checkpoint from Leader

bharatviswa504 commented on a change in pull request #1002: URL: https://github.com/apache/hadoop-ozone/pull/1002#discussion_r437858630 ## File path: hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java ## @@ -3113,27 +3120,32 @@ private DBChec

[jira] [Updated] (HDDS-741) all containers are in 'CLOSING' state after service restart

[ https://issues.apache.org/jira/browse/HDDS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-741: - Labels: TriagePending (was: TriagePending test-badlands) > all containers are in 'CLOSING' state after ser

[jira] [Updated] (HDDS-1169) Add MetricSource Support to SCM metrics

[ https://issues.apache.org/jira/browse/HDDS-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1169: -- Target Version/s: 0.7.0 (was: 0.6.0) > Add MetricSource Support to SCM metrics > --

[jira] [Updated] (HDDS-1131) destroy pipeline failed with PipelineNotFoundException

[ https://issues.apache.org/jira/browse/HDDS-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1131: -- Labels: TriagePending (was: TriagePending pushed-to-craterlake test-badlands) > destroy pipeline faile

[jira] [Updated] (HDDS-1169) Add MetricSource Support to SCM metrics

[ https://issues.apache.org/jira/browse/HDDS-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1169: -- Labels: (was: Triaged) > Add MetricSource Support to SCM metrics > ---

[jira] [Assigned] (HDDS-1556) SCM should update leader information of a pipeline from pipeline report

[ https://issues.apache.org/jira/browse/HDDS-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar reassigned HDDS-1556: - Assignee: Nanda kumar > SCM should update leader information of a pipeline from pipeline report >

[jira] [Updated] (HDDS-2641) Allow SCM webUI to show decommision and maintenance nodes

[ https://issues.apache.org/jira/browse/HDDS-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-2641: -- Labels: (was: TriagePending) > Allow SCM webUI to show decommision and maintenance nodes > ---

[jira] [Updated] (HDDS-2641) Allow SCM webUI to show decommision and maintenance nodes

[ https://issues.apache.org/jira/browse/HDDS-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-2641: -- Target Version/s: 0.7.0 (was: 0.6.0) > Allow SCM webUI to show decommision and maintenance nodes >

[jira] [Updated] (HDDS-2673) Merge MockNodeManager and SimpleMockNodeManager

[ https://issues.apache.org/jira/browse/HDDS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-2673: -- Labels: (was: TriagePending) > Merge MockNodeManager and SimpleMockNodeManager > -

[jira] [Updated] (HDDS-2673) Merge MockNodeManager and SimpleMockNodeManager

[ https://issues.apache.org/jira/browse/HDDS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-2673: -- Target Version/s: 0.7.0 (was: 0.6.0) > Merge MockNodeManager and SimpleMockNodeManager > --

[jira] [Updated] (HDDS-2642) Expose decommission / maintenance metrics via JMX

[ https://issues.apache.org/jira/browse/HDDS-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-2642: -- Labels: (was: TriagePending) > Expose decommission / maintenance metrics via JMX > ---

[jira] [Updated] (HDDS-2642) Expose decommission / maintenance metrics via JMX

[ https://issues.apache.org/jira/browse/HDDS-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-2642: -- Target Version/s: 0.7.0 (was: 0.6.0) > Expose decommission / maintenance metrics via JMX >

[jira] [Commented] (HDDS-3096) SCM does not exit Safe mode

[ https://issues.apache.org/jira/browse/HDDS-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130051#comment-17130051 ] Nanda kumar commented on HDDS-3096: --- Duplicate of HDDS-3039? > SCM does not exit Safe m

[jira] [Updated] (HDDS-3080) Configurable container placement policy may not be compatible with pipeline placement policy

[ https://issues.apache.org/jira/browse/HDDS-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-3080: -- Target Version/s: 0.7.0 (was: 0.6.0) > Configurable container placement policy may not be compatible wi

[jira] [Updated] (HDDS-3107) Pipelines may not be rack aware on cluster startup

[ https://issues.apache.org/jira/browse/HDDS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-3107: -- Target Version/s: 0.7.0 (was: 0.6.0) > Pipelines may not be rack aware on cluster startup > ---

[jira] [Updated] (HDDS-3345) Investigate failure of TestDecommissionAndMaintenance integration test

[ https://issues.apache.org/jira/browse/HDDS-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-3345: -- Target Version/s: 0.7.0 (was: 0.6.0) > Investigate failure of TestDecommissionAndMaintenance integratio

[jira] [Updated] (HDDS-1880) Decommissioining and maintenance mode in Ozone

[ https://issues.apache.org/jira/browse/HDDS-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1880: -- Labels: (was: TriagePending) > Decommissioining and maintenance mode in Ozone > -

[jira] [Updated] (HDDS-3485) Use typesafe ContainerID instead of long value

[ https://issues.apache.org/jira/browse/HDDS-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-3485: -- Labels: (was: TriagePending) > Use typesafe ContainerID instead of long value > --

[jira] [Updated] (HDDS-3485) Use typesafe ContainerID instead of long value

[ https://issues.apache.org/jira/browse/HDDS-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-3485: -- Target Version/s: 0.7.0 (was: 0.6.0) > Use typesafe ContainerID instead of long value > ---

[GitHub] [hadoop-ozone] GlenGeng commented on a change in pull request #1041: HDDS-3725. Ozone sh volume client support quota option

GlenGeng commented on a change in pull request #1041: URL: https://github.com/apache/hadoop-ozone/pull/1041#discussion_r437846415 ## File path: hadoop-ozone/client/src/main/java/org/apache/hadoop/ozone/client/VolumeArgs.java ## @@ -107,7 +118,8 @@ public String getQuota() {

[jira] [Resolved] (HDDS-2564) Handle InterruptedException in ContainerStateMachine

[ https://issues.apache.org/jira/browse/HDDS-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Chitlangia resolved HDDS-2564. - Fix Version/s: 0.6.0 Resolution: Fixed > Handle InterruptedException in ContainerSt

[jira] [Updated] (HDDS-3771) Block when using ’ozone fs -cat o3fs://xxxxx.xxxx/xxx‘

[ https://issues.apache.org/jira/browse/HDDS-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mingchao zhao updated HDDS-3771: Description: Block when I use ’ozone fs -cat o3fs://x./xxx‘. And no logs are seen in the ba

[jira] [Created] (HDDS-3771) Block when using ’ozone fs -cat o3fs://xxxxx.xxxx/xxx‘

mingchao zhao created HDDS-3771: --- Summary: Block when using ’ozone fs -cat o3fs://x./xxx‘ Key: HDDS-3771 URL: https://issues.apache.org/jira/browse/HDDS-3771 Project: Hadoop Distributed Data Stor

[jira] [Updated] (HDDS-3771) Block when using ’ozone fs -cat o3fs://xxxxx.xxxx/xxx‘

[ https://issues.apache.org/jira/browse/HDDS-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mingchao zhao updated HDDS-3771: Attachment: image-2020-06-10-11-48-12-299.png > Block when using ’ozone fs -cat o3fs://x./xx

[GitHub] [hadoop-ozone] runzhiwang commented on pull request #1048: HDDS-3481. SCM ask too many datanodes to replicate the same container

runzhiwang commented on pull request #1048: URL: https://github.com/apache/hadoop-ozone/pull/1048#issuecomment-641701943 @nandakumar131 @arp7 Could you help review this patch ? Thank you very much. This is an automated messag

[GitHub] [hadoop-ozone] xiaoyuyao commented on pull request #1043: HDDS-3760. Avoid UUID#toString call in Pipeline#getProtobufMessage

xiaoyuyao commented on pull request #1043: URL: https://github.com/apache/hadoop-ozone/pull/1043#issuecomment-641690016 LGTM, +1. This is an automated message from the Apache Git Service. To respond to the message, please lo

[jira] [Updated] (HDDS-3481) SCM ask too many datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3481: - Labels: TriagePending pull-request-available (was: TriagePending) > SCM ask too many datanodes to

[GitHub] [hadoop-ozone] runzhiwang opened a new pull request #1048: HDDS-3481. SCM ask too many datanodes to replicate the same container

runzhiwang opened a new pull request #1048: URL: https://github.com/apache/hadoop-ozone/pull/1048 ## What changes were proposed in this pull request? 1. increase replication timeout. 2. if datanode is not healthy, remove the replicate action from inflightActions ## What i

[jira] [Updated] (HDDS-3481) SCM ask too many datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Summary: SCM ask too many datanodes to replicate the same container (was: SCM ask 31 datanodes to replica

[GitHub] [hadoop-ozone] runzhiwang commented on pull request #1028: HDDS-3735. Improve SCM performance with 3.7% by remove unnecessary lock and unlock

runzhiwang commented on pull request #1028: URL: https://github.com/apache/hadoop-ozone/pull/1028#issuecomment-641678745 @elek Could you help review this patch ? Thank you very much. This is an automated message from the Apac

[GitHub] [hadoop-ozone] hanishakoneru commented on pull request #1004: HDDS-3639. Maintain FileHandle Information in OMMetadataManager.

hanishakoneru commented on pull request #1004: URL: https://github.com/apache/hadoop-ozone/pull/1004#issuecomment-641677419 Thanks for working on this @prashantpogde. +1 for merging into branch HDDS-3001, pending CI. This

[GitHub] [hadoop-ozone] hanishakoneru commented on a change in pull request #1004: HDDS-3639. Maintain FileHandle Information in OMMetadataManager.

hanishakoneru commented on a change in pull request #1004: URL: https://github.com/apache/hadoop-ozone/pull/1004#discussion_r437820153 ## File path: hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/key/OMKeyRenameResponse.java ## @@ -93,6 +93,15 @@

[jira] [Updated] (HDDS-3770) Improve discardPipeline

[ https://issues.apache.org/jira/browse/HDDS-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3770: - Description: !screenshot-1.png! > Improve discardPipeline > --- > >

[jira] [Updated] (HDDS-3770) Improve discardPipeline

[ https://issues.apache.org/jira/browse/HDDS-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3770: - Attachment: screenshot-1.png > Improve discardPipeline > --- > > Key:

[jira] [Created] (HDDS-3770) Improve discardPipeline

runzhiwang created HDDS-3770: Summary: Improve discardPipeline Key: HDDS-3770 URL: https://issues.apache.org/jira/browse/HDDS-3770 Project: Hadoop Distributed Data Store Issue Type: Sub-task

[GitHub] [hadoop-ozone] runzhiwang commented on pull request #1031: HDDS-3745. Improve OM and SCM performance with 64% by avoid call getServiceInfo in s3g

runzhiwang commented on pull request #1031: URL: https://github.com/apache/hadoop-ozone/pull/1031#issuecomment-641665483 @elek Could you help review this patch ? Thank you very much. This is an automated message from the Apac

[jira] [Updated] (HDDS-2873) hdds.x509.CRL.name missing from ozone-default.xml

[ https://issues.apache.org/jira/browse/HDDS-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoyu Yao updated HDDS-2873: - Target Version/s: 0.7.0 (was: 0.6.0) > hdds.x509.CRL.name missing from ozone-default.xml > --

[jira] [Updated] (HDDS-2873) hdds.x509.CRL.name missing from ozone-default.xml

[ https://issues.apache.org/jira/browse/HDDS-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoyu Yao updated HDDS-2873: - Parent: HDDS-2731 Issue Type: Sub-task (was: Bug) > hdds.x509.CRL.name missing from ozone-default

[jira] [Commented] (HDDS-2867) Generic Extensible Token support for Ozone

[ https://issues.apache.org/jira/browse/HDDS-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129908#comment-17129908 ] Xiaoyu Yao commented on HDDS-2867: -- Move to 0.7.0 > Generic Extensible Token support for

[jira] [Updated] (HDDS-2867) Generic Extensible Token support for Ozone

[ https://issues.apache.org/jira/browse/HDDS-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoyu Yao updated HDDS-2867: - Labels: Triaged (was: TriagePending) > Generic Extensible Token support for Ozone > -

[jira] [Updated] (HDDS-2867) Generic Extensible Token support for Ozone

[ https://issues.apache.org/jira/browse/HDDS-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoyu Yao updated HDDS-2867: - Target Version/s: 0.7.0 (was: 0.6.0) > Generic Extensible Token support for Ozone > -

[jira] [Updated] (HDDS-2496) Delegate Ozone volume create/list ACL check to authorizer plugin

[ https://issues.apache.org/jira/browse/HDDS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoyu Yao updated HDDS-2496: - Labels: Triaged (was: TriagePending) > Delegate Ozone volume create/list ACL check to authorizer plugin >

  1   2   3   4   >