[jira] [Resolved] (HDFS-15610) Reduce datanode upgrade/hardlink thread

[ https://issues.apache.org/jira/browse/HDFS-15610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved HDFS-15610. Fix Version/s: 3.4.0 Resolution: Fixed > Reduce datanode upgrade/hardlink thread >

[jira] [Created] (HDFS-15401) Namenode should log warning if concat/append finds file with large number of blocks

Lokesh Jain created HDFS-15401: -- Summary: Namenode should log warning if concat/append finds file with large number of blocks Key: HDFS-15401 URL: https://issues.apache.org/jira/browse/HDFS-15401

[jira] [Created] (HDFS-15400) fsck should log a warning if it finds a file with large number of blocks

Lokesh Jain created HDFS-15400: -- Summary: fsck should log a warning if it finds a file with large number of blocks Key: HDFS-15400 URL: https://issues.apache.org/jira/browse/HDFS-15400 Project: Hadoop

[jira] [Created] (HDFS-15392) DistrbutedFileSystem#concat api can create large number of small blocks

Lokesh Jain created HDFS-15392: -- Summary: DistrbutedFileSystem#concat api can create large number of small blocks Key: HDFS-15392 URL: https://issues.apache.org/jira/browse/HDFS-15392 Project: Hadoop

[jira] [Resolved] (HDFS-15201) SnapshotCounter hits MaxSnapshotID limit

[ https://issues.apache.org/jira/browse/HDFS-15201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved HDFS-15201. Resolution: Fixed > SnapshotCounter hits MaxSnapshotID limit >

[jira] [Resolved] (HDDS-2347) XCeiverClientGrpc's parallel use leads to NPE

[ https://issues.apache.org/jira/browse/HDDS-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved HDDS-2347. --- Fix Version/s: 0.5.0 Resolution: Fixed > XCeiverClientGrpc's parallel use leads to NPE >

[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 ] Lokesh Jain updated HDDS-2342: -- Description: In a heap dump many threads in ContainerStateMachine$chunkExecutor holds onto native

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

Lokesh Jain created HDDS-2342: - Summary: ContainerStateMachine$chunkExecutor threads hold onto native memory Key: HDDS-2342 URL: https://issues.apache.org/jira/browse/HDDS-2342 Project: Hadoop

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

[ https://issues.apache.org/jira/browse/HDDS-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955757#comment-16955757 ] Lokesh Jain commented on HDDS-2332: --- [~cxorm] It is difficult to reproduce the issue. I saw it in one of

[jira] [Commented] (HDDS-2328) Support large-scale listing

[ https://issues.apache.org/jira/browse/HDDS-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955756#comment-16955756 ] Lokesh Jain commented on HDDS-2328: --- Currently we do not implement FileSystem#listLocatedStatus api in

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

[ https://issues.apache.org/jira/browse/HDDS-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954689#comment-16954689 ] Lokesh Jain commented on HDDS-2332: --- Should we support timeout in client as well which works if ratis

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

Lokesh Jain created HDDS-2332: - Summary: BlockOutputStream#waitOnFlushFutures blocks on putBlock combined future Key: HDDS-2332 URL: https://issues.apache.org/jira/browse/HDDS-2332 Project: Hadoop

[jira] [Updated] (HDDS-2299) BlockManager should allocate a block in excluded pipelines if none other left

[ https://issues.apache.org/jira/browse/HDDS-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-2299: -- Description: In SCM, BlockManager#allocateBlock does not allocate a block in the excluded pipelines or

[jira] [Created] (HDDS-2299) BlockManager should allocate a block in excluded pipelines if none other left

Lokesh Jain created HDDS-2299: - Summary: BlockManager should allocate a block in excluded pipelines if none other left Key: HDDS-2299 URL: https://issues.apache.org/jira/browse/HDDS-2299 Project: Hadoop

[jira] [Commented] (HDDS-2186) Fix tests using MiniOzoneCluster for its memory related exceptions

[ https://issues.apache.org/jira/browse/HDDS-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939290#comment-16939290 ] Lokesh Jain commented on HDDS-2186: --- [~timmylicheng] You are right. This might be related to multiple

[jira] [Assigned] (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 ] Lokesh Jain reassigned HDDS-2189: - Assignee: Lokesh Jain > Datanode should send PipelineAction on RaftServer failure >

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

Lokesh Jain created HDDS-2189: - Summary: Datanode should send PipelineAction on RaftServer failure Key: HDDS-2189 URL: https://issues.apache.org/jira/browse/HDDS-2189 Project: Hadoop Distributed Data

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937742#comment-16937742 ] Lokesh Jain commented on HDDS-1868: --- [~swagle] Thanks for updating the patch! The changes look good to

[jira] [Updated] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1868: -- Status: Open (was: Patch Available) > Ozone pipelines should be marked as ready only after the leader

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933383#comment-16933383 ] Lokesh Jain commented on HDDS-1868: --- [~swagle] I think there is a case where it is not handled. There

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932224#comment-16932224 ] Lokesh Jain commented on HDDS-1868: --- [~swagle] Thanks for working on this! I think we should include

[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 ] Lokesh Jain updated HDDS-2117: -- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (HDDS-2114) Rename does not preserve non-explicitly created interim directories

[ https://issues.apache.org/jira/browse/HDDS-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-2114: -- Status: Patch Available (was: Open) > Rename does not preserve non-explicitly created interim

[jira] [Updated] (HDDS-2103) TestContainerReplication fails due to unhealthy container

[ https://issues.apache.org/jira/browse/HDDS-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-2103: -- Fix Version/s: 0.5.0 Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927278#comment-16927278 ] Lokesh Jain commented on HDDS-1868: --- ContainerStateMachine already has an api called notifyLeader which

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926426#comment-16926426 ] Lokesh Jain commented on HDDS-1868: --- [~swagle] The changes look good to me. I am not able to open the

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925401#comment-16925401 ] Lokesh Jain commented on HDDS-1868: --- [~swagle] In the patch below condition would only be true for the

[jira] [Commented] (HDDS-1899) DeleteBlocksCommandHandler is unable to find the container in SCM

[ https://issues.apache.org/jira/browse/HDDS-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924282#comment-16924282 ] Lokesh Jain commented on HDDS-1899: --- [~nandakumar131] I think the exception seems harmless. This

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923635#comment-16923635 ] Lokesh Jain commented on HDDS-1868: --- On restart, SCM marks the pipeline as OPEN only if all the

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923519#comment-16923519 ] Lokesh Jain commented on HDDS-1868: --- [~swagle] Thanks for working on this! I think leaderInfo in 

[jira] [Updated] (HDDS-1561) Mark OPEN containers as QUASI_CLOSED as part of Ratis groupRemove

[ https://issues.apache.org/jira/browse/HDDS-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1561: -- Status: Patch Available (was: Open) > Mark OPEN containers as QUASI_CLOSED as part of Ratis

[jira] [Commented] (HDDS-1561) Mark OPEN containers as QUASI_CLOSED as part of Ratis groupRemove

[ https://issues.apache.org/jira/browse/HDDS-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922496#comment-16922496 ] Lokesh Jain commented on HDDS-1561: --- The Jira needs a ratis snapshot upgrade. Uploaded a patch without

[jira] [Updated] (HDDS-1561) Mark OPEN containers as QUASI_CLOSED as part of Ratis groupRemove

[ https://issues.apache.org/jira/browse/HDDS-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1561: -- Attachment: HDDS-1561.001.patch > Mark OPEN containers as QUASI_CLOSED as part of Ratis groupRemove >

[jira] [Updated] (HDDS-2048) State check during container state transition in datanode should be lock protected

[ https://issues.apache.org/jira/browse/HDDS-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-2048: -- Status: Patch Available (was: Open) > State check during container state transition in datanode should

[jira] [Created] (HDDS-2048) State check during container state transition in datanode should be lock protected

Lokesh Jain created HDDS-2048: - Summary: State check during container state transition in datanode should be lock protected Key: HDDS-2048 URL: https://issues.apache.org/jira/browse/HDDS-2048 Project:

[jira] [Commented] (HDDS-1553) Add metrics in rack aware container placement policy

[ https://issues.apache.org/jira/browse/HDDS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916620#comment-16916620 ] Lokesh Jain commented on HDDS-1553: --- [~Sammi] Can you please attach a link to the PR? > Add metrics in

[jira] [Updated] (HDDS-1981) Datanode should sync db when container is moved to CLOSED or QUASI_CLOSED state

[ https://issues.apache.org/jira/browse/HDDS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1981: -- Fix Version/s: 0.5.0 > Datanode should sync db when container is moved to CLOSED or QUASI_CLOSED >

[jira] [Updated] (HDDS-1981) Datanode should sync db when container is moved to CLOSED or QUASI_CLOSED state

[ https://issues.apache.org/jira/browse/HDDS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1981: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Datanode should sync db when

[jira] [Updated] (HDDS-1981) Datanode should sync db when container is moved to CLOSED or QUASI_CLOSED state

[ https://issues.apache.org/jira/browse/HDDS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1981: -- Status: Patch Available (was: Open) > Datanode should sync db when container is moved to CLOSED or

[jira] [Updated] (HDDS-1959) Decrement purge interval for Ratis logs in datanode

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1959: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Decrement purge interval for Ratis

[jira] [Updated] (HDDS-1959) Decrement purge interval for Ratis logs in datanode

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1959: -- Fix Version/s: 0.5.0 > Decrement purge interval for Ratis logs in datanode >

[jira] [Updated] (HDDS-1959) Decrement purge interval for Ratis logs in datanode

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1959: -- Status: Patch Available (was: Open) > Decrement purge interval for Ratis logs in datanode >

[jira] [Comment Edited] (HDDS-1959) Decrement purge interval for Ratis logs in datanode

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907886#comment-16907886 ] Lokesh Jain edited comment on HDDS-1959 at 8/15/19 7:33 AM: [~pingsutw] Sorry!

[jira] [Updated] (HDDS-1959) Decrement purge interval for Ratis logs in datanode

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1959: -- Description: Currently purge interval for ratis log("dfs.container.ratis.log.purge.gap") is set at

[jira] [Updated] (HDDS-1959) Decrement purge interval for Ratis logs in datanode

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1959: -- Summary: Decrement purge interval for Ratis logs in datanode (was: Decrement purge interval for Ratis

[jira] [Updated] (HDDS-1959) Decrement purge interval for Ratis logs

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1959: -- Description: Currently purge interval for ratis log("dfs.container.ratis.log.purge.gap") is set at

[jira] [Commented] (HDDS-1959) Decrement purge interval for Ratis logs

[ https://issues.apache.org/jira/browse/HDDS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907886#comment-16907886 ] Lokesh Jain commented on HDDS-1959: --- [~pingsutw] Sorry! I had posted the wrong configuration in the

[jira] [Created] (HDDS-1959) Decrement purge interval for Ratis logs

Lokesh Jain created HDDS-1959: - Summary: Decrement purge interval for Ratis logs Key: HDDS-1959 URL: https://issues.apache.org/jira/browse/HDDS-1959 Project: Hadoop Distributed Data Store Issue

[jira] [Commented] (HDFS-14692) Upload button should not encode complete url

[ https://issues.apache.org/jira/browse/HDFS-14692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898275#comment-16898275 ] Lokesh Jain commented on HDFS-14692: The patch fixes the issue by encoding just the directory part in

[jira] [Updated] (HDFS-14692) Upload button should not encode complete url

[ https://issues.apache.org/jira/browse/HDFS-14692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDFS-14692: --- Status: Patch Available (was: Open) > Upload button should not encode complete url >

[jira] [Updated] (HDFS-14692) Upload button should not encode complete url

[ https://issues.apache.org/jira/browse/HDFS-14692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDFS-14692: --- Attachment: HDFS-14692.001.patch > Upload button should not encode complete url >

[jira] [Created] (HDFS-14692) Upload button should not encode complete url

Lokesh Jain created HDFS-14692: -- Summary: Upload button should not encode complete url Key: HDFS-14692 URL: https://issues.apache.org/jira/browse/HDFS-14692 Project: Hadoop HDFS Issue Type: Bug

[jira] [Comment Edited] (HDDS-1834) parent directories not found in secure setup due to ACL check

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892790#comment-16892790 ] Lokesh Jain edited comment on HDDS-1834 at 7/25/19 2:14 PM: There are two bugs

[jira] [Commented] (HDDS-1834) parent directories not found in secure setup due to ACL check

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892790#comment-16892790 ] Lokesh Jain commented on HDDS-1834: --- The problem exists in general for checkAccess. There are two bugs

[jira] [Commented] (HDDS-1834) ozone fs -mkdir -p does not create parent directories in ozonesecure

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892634#comment-16892634 ] Lokesh Jain commented on HDDS-1834: --- HDDS-1481 changes the mkdir logic for OzoneFileSystem. Earlier all

[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 ] Lokesh Jain updated HDDS-1816: -- Status: Patch Available (was: Open) > ContainerStateMachine should limit number of pending apply

[jira] [Commented] (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:comment-tabpanel=16890287#comment-16890287 ] Lokesh Jain commented on HDDS-1816: --- [~nandakumar131] it is good to have but not a blocker for 0.4.1

[jira] [Assigned] (HDDS-1834) ozone fs -mkdir -p does not create parent directories in ozonesecure

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain reassigned HDDS-1834: - Assignee: (was: Lokesh Jain) > ozone fs -mkdir -p does not create parent directories in

[jira] [Comment Edited] (HDDS-1834) ozone fs -mkdir -p does not create parent directories

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888798#comment-16888798 ] Lokesh Jain edited comment on HDDS-1834 at 7/19/19 11:28 AM: - [~adoroszlai]

[jira] [Commented] (HDDS-1834) ozone fs -mkdir -p does not create parent directories

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888798#comment-16888798 ] Lokesh Jain commented on HDDS-1834: --- [~adoroszlai] Thanks for reporting the issue! On my local setup it

[jira] [Assigned] (HDDS-1834) ozone fs -mkdir -p does not create parent directories

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain reassigned HDDS-1834: - Assignee: Lokesh Jain > ozone fs -mkdir -p does not create parent directories >

[jira] [Created] (HDDS-1824) IllegalArgumentException in NetworkTopologyImpl causes SCM to shutdown

Lokesh Jain created HDDS-1824: - Summary: IllegalArgumentException in NetworkTopologyImpl causes SCM to shutdown Key: HDDS-1824 URL: https://issues.apache.org/jira/browse/HDDS-1824 Project: Hadoop

[jira] [Updated] (HDDS-1767) ContainerStateMachine should have its own executors for executing applyTransaction calls

[ https://issues.apache.org/jira/browse/HDDS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1767: -- Resolution: Fixed Status: Resolved (was: Patch Available) > ContainerStateMachine should have

[jira] [Updated] (HDDS-1481) Cleanup BasicOzoneFileSystem#mkdir

[ https://issues.apache.org/jira/browse/HDDS-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1481: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Cleanup BasicOzoneFileSystem#mkdir

[jira] [Updated] (HDDS-1481) Cleanup BasicOzoneFileSystem#mkdir

[ https://issues.apache.org/jira/browse/HDDS-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1481: -- Status: Patch Available (was: Open) > Cleanup BasicOzoneFileSystem#mkdir >

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

Lokesh Jain created HDDS-1816: - Summary: ContainerStateMachine should limit number of pending apply transactions Key: HDDS-1816 URL: https://issues.apache.org/jira/browse/HDDS-1816 Project: Hadoop

[jira] [Updated] (HDDS-1767) ContainerStateMachine should have its own executors for executing applyTransaction calls

[ https://issues.apache.org/jira/browse/HDDS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1767: -- Status: Patch Available (was: Open) > ContainerStateMachine should have its own executors for

[jira] [Updated] (HDDS-1767) ContainerStateMachine should have its own executors for executing applyTransaction calls

[ https://issues.apache.org/jira/browse/HDDS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1767: -- Labels: pull-request-available (was: ) > ContainerStateMachine should have its own executors for

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

[ https://issues.apache.org/jira/browse/HDDS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain moved RATIS-620 to HDDS-1779: - Fix Version/s: (was: 0.4.0) Affects Version/s: (was: 0.4.0)

[jira] [Created] (HDDS-1767) ContainerStateMachine should have its own executors for executing applyTransaction calls

Lokesh Jain created HDDS-1767: - Summary: ContainerStateMachine should have its own executors for executing applyTransaction calls Key: HDDS-1767 URL: https://issues.apache.org/jira/browse/HDDS-1767

[jira] [Created] (HDDS-1766) ContainerStateMachine is unable to increment lastAppliedIndex

Lokesh Jain created HDDS-1766: - Summary: ContainerStateMachine is unable to increment lastAppliedIndex Key: HDDS-1766 URL: https://issues.apache.org/jira/browse/HDDS-1766 Project: Hadoop Distributed Data

[jira] [Created] (HDDS-1750) Add block allocation metric for pipelines in SCM

Lokesh Jain created HDDS-1750: - Summary: Add block allocation metric for pipelines in SCM Key: HDDS-1750 URL: https://issues.apache.org/jira/browse/HDDS-1750 Project: Hadoop Distributed Data Store

[jira] [Created] (HDDS-1626) Optimize allocateBlock for cases when excludeList is provided

Lokesh Jain created HDDS-1626: - Summary: Optimize allocateBlock for cases when excludeList is provided Key: HDDS-1626 URL: https://issues.apache.org/jira/browse/HDDS-1626 Project: Hadoop Distributed Data

[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem

[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1461: -- Resolution: Fixed Fix Version/s: 0.5.0 Status: Resolved (was: Patch Available) >

[jira] [Updated] (HDDS-1503) Reduce garbage generated by non-netty threads in datanode ratis server

[ https://issues.apache.org/jira/browse/HDDS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1503: -- Resolution: Fixed Fix Version/s: 0.5.0 Status: Resolved (was: Patch Available) >

[jira] [Updated] (HDDS-1503) Reduce garbage generated by non-netty threads in datanode ratis server

[ https://issues.apache.org/jira/browse/HDDS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1503: -- Status: Patch Available (was: Open) > Reduce garbage generated by non-netty threads in datanode ratis

[jira] [Resolved] (HDFS-12735) Make ContainerStateMachine#applyTransaction async

[ https://issues.apache.org/jira/browse/HDFS-12735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved HDFS-12735. Resolution: Duplicate > Make ContainerStateMachine#applyTransaction async >

[jira] [Created] (HDDS-1503) Reduce garbage generated by non-netty threads in datanode ratis server

Lokesh Jain created HDDS-1503: - Summary: Reduce garbage generated by non-netty threads in datanode ratis server Key: HDDS-1503 URL: https://issues.apache.org/jira/browse/HDDS-1503 Project: Hadoop

[jira] [Created] (HDDS-1481) Cleanup BasicOzoneFileSystem#mkdir

Lokesh Jain created HDDS-1481: - Summary: Cleanup BasicOzoneFileSystem#mkdir Key: HDDS-1481 URL: https://issues.apache.org/jira/browse/HDDS-1481 Project: Hadoop Distributed Data Store Issue Type:

[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem

[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1461: -- Status: Patch Available (was: Open) > Optimize listStatus api in OzoneFileSystem >

[jira] [Updated] (HDDS-1460) Add the optmizations of HDDS-1300 to BasicOzoneFileSystem

[ https://issues.apache.org/jira/browse/HDDS-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1460: -- Resolution: Fixed Fix Version/s: 0.5.0 Status: Resolved (was: Patch Available) > Add

[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem

[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1461: -- Summary: Optimize listStatus api in OzoneFileSystem (was: Optimize listStatus api in OzoneFileStatus)

[jira] [Created] (HDDS-1461) Optimize listStatus api in OzoneFileStatus

Lokesh Jain created HDDS-1461: - Summary: Optimize listStatus api in OzoneFileStatus Key: HDDS-1461 URL: https://issues.apache.org/jira/browse/HDDS-1461 Project: Hadoop Distributed Data Store

[jira] [Created] (HDDS-1460) Add the optmizations of HDDS-1300 to BasicOzoneFileSystem

Lokesh Jain created HDDS-1460: - Summary: Add the optmizations of HDDS-1300 to BasicOzoneFileSystem Key: HDDS-1460 URL: https://issues.apache.org/jira/browse/HDDS-1460 Project: Hadoop Distributed Data

[jira] [Commented] (HDDS-1448) RatisPipelineProvider should only consider open pipeline while excluding dn for pipeline allocation

[ https://issues.apache.org/jira/browse/HDDS-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823698#comment-16823698 ] Lokesh Jain commented on HDDS-1448: --- The changes required for this Jira would enable multiple three node

[jira] [Resolved] (HDDS-1405) ITestOzoneContractCreate is failing

[ https://issues.apache.org/jira/browse/HDDS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved HDDS-1405. --- Resolution: Resolved > ITestOzoneContractCreate is failing > --- > >

[jira] [Created] (HDDS-1405) ITestOzoneContractCreate is failing

Lokesh Jain created HDDS-1405: - Summary: ITestOzoneContractCreate is failing Key: HDDS-1405 URL: https://issues.apache.org/jira/browse/HDDS-1405 Project: Hadoop Distributed Data Store Issue

[jira] [Updated] (HDDS-1301) Optimize recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1301: -- Status: Patch Available (was: Open) > Optimize recursive ozone filesystem apis >

[jira] [Commented] (HDDS-1301) Optimize recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812538#comment-16812538 ] Lokesh Jain commented on HDDS-1301: --- Uploaded v1 patch for review. Will create pull request for the

[jira] [Updated] (HDDS-1301) Optimize recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1301: -- Attachment: HDDS-1301.001.patch > Optimize recursive ozone filesystem apis >

[jira] [Commented] (HDDS-1294) ExcludeList shoud be a RPC Client config so that multiple streams can avoid the same error.

[ https://issues.apache.org/jira/browse/HDDS-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811164#comment-16811164 ] Lokesh Jain commented on HDDS-1294: --- [~shashikant] Thanks for updating the patch! In

[jira] [Commented] (HDDS-1294) ExcludeList shoud be a RPC Client config so that multiple streams can avoid the same error.

[ https://issues.apache.org/jira/browse/HDDS-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810704#comment-16810704 ] Lokesh Jain commented on HDDS-1294: --- [~shashikant] Thanks for working on this! The patch looks good to

[jira] [Commented] (HDDS-1349) Remove watchClient from XceiverClientRatis

[ https://issues.apache.org/jira/browse/HDDS-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809500#comment-16809500 ] Lokesh Jain commented on HDDS-1349: --- [~shashikant] Thanks for working on this! The patch looks good to

[jira] [Reopened] (HDDS-1134) OzoneFileSystem#create should allocate alteast one block for future writes.

[ https://issues.apache.org/jira/browse/HDDS-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain reopened HDDS-1134: --- Reopening issue as it was not fixed in HDDS-1300. > OzoneFileSystem#create should allocate alteast one

[jira] [Updated] (HDDS-1300) Optimize non-recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1300: -- Resolution: Resolved Status: Resolved (was: Patch Available) > Optimize non-recursive ozone

[jira] [Updated] (HDDS-1300) Optimize non-recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1300: -- Fix Version/s: 0.5.0 > Optimize non-recursive ozone filesystem apis >

[jira] [Commented] (HDDS-1300) Optimize non-recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805006#comment-16805006 ] Lokesh Jain commented on HDDS-1300: --- [~msingh] [~bharatviswa] Thanks for reviewing the patch! I have

[jira] [Commented] (HDDS-1300) Optimize non-recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804739#comment-16804739 ] Lokesh Jain commented on HDDS-1300: --- [~bharatviswa] Thanks for reviewing the patch! v8 patch removes the

[jira] [Updated] (HDDS-1300) Optimize non-recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1300: -- Attachment: HDDS-1300.008.patch > Optimize non-recursive ozone filesystem apis >

[jira] [Commented] (HDDS-1300) Optimize non-recursive ozone filesystem apis

[ https://issues.apache.org/jira/browse/HDDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803954#comment-16803954 ] Lokesh Jain commented on HDDS-1300: --- [~msingh] Based on offline discussion v7 patch avoids allocateBlock

  1   2   3   4   5   6   7   8   9   10   >