[jira] [Updated] (HDDS-3623) Implement getReadCopy in Table.

[ https://issues.apache.org/jira/browse/HDDS-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3623: - Description: Introduce a getReadCopy in table method. As right now, get when a value

[jira] [Updated] (HDDS-3615) Call cleanup on tables only when double buffer has transactions related to tables.

[ https://issues.apache.org/jira/browse/HDDS-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3615: - Status: Patch Available (was: Open) > Call cleanup on tables only when double buffer has

[jira] [Updated] (HDDS-3623) Implement getReadCopy in Table.

[ https://issues.apache.org/jira/browse/HDDS-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3623: - Status: Patch Available (was: Open) > Implement getReadCopy in Table. >

[jira] [Updated] (HDDS-3614) Remove S3Table from OmMetadataManager

[ https://issues.apache.org/jira/browse/HDDS-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3614: - Status: Patch Available (was: Open) > Remove S3Table from OmMetadataManager >

[jira] [Created] (HDDS-3623) Implement getReadCopy in Table.

Bharat Viswanadham created HDDS-3623: Summary: Implement getReadCopy in Table. Key: HDDS-3623 URL: https://issues.apache.org/jira/browse/HDDS-3623 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-3623) Implement getReadCopy in Table.

[ https://issues.apache.org/jira/browse/HDDS-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3623: - Issue Type: New Feature (was: Bug) > Implement getReadCopy in Table. >

[jira] [Updated] (HDDS-3615) Call cleanup on tables only when double buffer has transactions related to tables.

[ https://issues.apache.org/jira/browse/HDDS-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3615: - Summary: Call cleanup on tables only when double buffer has transactions related to

[jira] [Updated] (HDDS-3615) Call cleanup on tables only when double buffer has transactions related to tables.

[ https://issues.apache.org/jira/browse/HDDS-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3615: - Description: For volume/bucket table currently it is full cache, and we need to cleanup

[jira] [Created] (HDDS-3615) Call cleanup for volume/bucket only when delete operations

Bharat Viswanadham created HDDS-3615: Summary: Call cleanup for volume/bucket only when delete operations Key: HDDS-3615 URL: https://issues.apache.org/jira/browse/HDDS-3615 Project: Hadoop

[jira] [Created] (HDDS-3614) Remove S3Table from OmMetadataManager

Bharat Viswanadham created HDDS-3614: Summary: Remove S3Table from OmMetadataManager Key: HDDS-3614 URL: https://issues.apache.org/jira/browse/HDDS-3614 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-3613) Fix JVMPause monitor start in OzoneManager

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

[jira] [Updated] (HDDS-3613) Fix JVMPause monitor start in OzoneManager

[ https://issues.apache.org/jira/browse/HDDS-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3613: - Status: Patch Available (was: In Progress) > Fix JVMPause monitor start in OzoneManager

[jira] [Created] (HDDS-3613) Fix JVMPause monitor start in OzoneManager

Bharat Viswanadham created HDDS-3613: Summary: Fix JVMPause monitor start in OzoneManager Key: HDDS-3613 URL: https://issues.apache.org/jira/browse/HDDS-3613 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-3580) Retry Cache in OM

[ https://issues.apache.org/jira/browse/HDDS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3580: - Issue Type: Improvement (was: Bug) > Retry Cache in OM > - > >

[jira] [Created] (HDDS-3580) Retry Cache in OM

Bharat Viswanadham created HDDS-3580: Summary: Retry Cache in OM Key: HDDS-3580 URL: https://issues.apache.org/jira/browse/HDDS-3580 Project: Hadoop Distributed Data Store Issue Type:

[jira] [Updated] (HDDS-3580) Retry Cache in OM

[ https://issues.apache.org/jira/browse/HDDS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3580: - Attachment: Retry Cache in OM.pdf > Retry Cache in OM > - > >

[jira] [Updated] (HDDS-3576) Use direct ratis config in OM Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3576: - Fix Version/s: (was: 0.5.0) > Use direct ratis config in OM Ratis Server >

[jira] [Commented] (HDDS-3576) Use direct ratis config in OM Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105831#comment-17105831 ] Bharat Viswanadham commented on HDDS-3576: -- This is similar to HDDS-2988 what we have done in

[jira] [Updated] (HDDS-3576) Use direct ratis config in OM Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3576: - Component/s: (was: Ozone Datanode) Ozone Manager

[jira] [Updated] (HDDS-3576) Use direct ratis config in OM Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3576: - Description: This Jira is to use getPropertiesByPrefix that match with "ozone.om.ratis"

[jira] [Updated] (HDDS-3576) Use direct ratis config in OM Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3576: - Labels: (was: pull-request-available teragentest) > Use direct ratis config in OM Ratis

[jira] [Assigned] (HDDS-3576) Use direct ratis config in OM Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3576: Assignee: (was: Bharat Viswanadham) > Use direct ratis config in OM Ratis

[jira] [Updated] (HDDS-3576) Use direct ratis config in OM Ratis Server

[ https://issues.apache.org/jira/browse/HDDS-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3576: - Issue Type: Improvement (was: Bug) > Use direct ratis config in OM Ratis Server >

[jira] [Created] (HDDS-3576) Use direct ratis config in OM Ratis Server

Bharat Viswanadham created HDDS-3576: Summary: Use direct ratis config in OM Ratis Server Key: HDDS-3576 URL: https://issues.apache.org/jira/browse/HDDS-3576 Project: Hadoop Distributed Data Store

[jira] [Resolved] (HDDS-3417) Enable TestSCMNodeManager#testScmNodeReportUpdate

[ https://issues.apache.org/jira/browse/HDDS-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3417. -- Fix Version/s: 0.6.0 Resolution: Fixed > Enable

[jira] [Resolved] (HDDS-3573) Update Ozone dependency hadoop.version to hadoop-3.2.1

[ https://issues.apache.org/jira/browse/HDDS-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3573. -- Fix Version/s: 0.6.0 Resolution: Fixed > Update Ozone dependency hadoop.version

[jira] [Updated] (HDDS-3217) Datanode startup is slow due to iterating container DB 2-3 times

[ https://issues.apache.org/jira/browse/HDDS-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3217: - Affects Version/s: 0.5.0 > Datanode startup is slow due to iterating container DB 2-3

[jira] [Updated] (HDDS-3217) Datanode startup is slow due to iterating container DB 2-3 times

[ https://issues.apache.org/jira/browse/HDDS-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3217: - Component/s: Ozone Datanode > Datanode startup is slow due to iterating container DB 2-3

[jira] [Updated] (HDDS-3217) Datanode startup is slow due to iterating container DB 2-3 times

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

[jira] [Updated] (HDDS-3513) Add OzoneConfiguration to UGI when startup S3Gateway

[ https://issues.apache.org/jira/browse/HDDS-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3513: - Component/s: (was: s3g) > Add OzoneConfiguration to UGI when startup S3Gateway >

[jira] [Updated] (HDDS-3513) Add OzoneConfiguration to UGI when startup S3Gateway

[ https://issues.apache.org/jira/browse/HDDS-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3513: - Component/s: s3g > Add OzoneConfiguration to UGI when startup S3Gateway >

[jira] [Updated] (HDDS-3513) Add OzoneConfiguration to UGI when startup S3Gateway

[ https://issues.apache.org/jira/browse/HDDS-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3513: - Component/s: S3 > Add OzoneConfiguration to UGI when startup S3Gateway >

[jira] [Updated] (HDDS-3513) Add OzoneConfiguration to UGI when startup S3Gateway

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

[jira] [Updated] (HDDS-3226) Tracing Ozone Manager DB write batch operations

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

[jira] [Resolved] (HDDS-3515) Ensure consistent OM token service field in HA environment

[ https://issues.apache.org/jira/browse/HDDS-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3515. -- Fix Version/s: 0.6.0 Resolution: Fixed > Ensure consistent OM token service

[jira] [Resolved] (HDDS-3223) Improve s3g read 1GB object efficiency by 100 times

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3223. -- Fix Version/s: 0.6.0 Resolution: Fixed > Improve s3g read 1GB object efficiency

[jira] [Updated] (HDDS-3375) S3A failing complete multipart upload with Ozone S3

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

[jira] [Updated] (HDDS-3334) OM Client failover to next OM on NotLeaderException

[ https://issues.apache.org/jira/browse/HDDS-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3334: - Fix Version/s: 0.6.0 > OM Client failover to next OM on NotLeaderException >

[jira] [Updated] (HDDS-3323) Hive fails to work with OM HA

[ https://issues.apache.org/jira/browse/HDDS-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3323: - Fix Version/s: (was: 0.6.0) > Hive fails to work with OM HA >

[jira] [Updated] (HDDS-3323) Hive fails to work with OM HA

[ https://issues.apache.org/jira/browse/HDDS-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3323: - Fix Version/s: 0.6.0 > Hive fails to work with OM HA > - > >

[jira] [Updated] (HDDS-3465) OM Failover retry happens too quickly when new leader suggested and retrying on same OM

[ https://issues.apache.org/jira/browse/HDDS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3465: - Fix Version/s: 0.6.0 > OM Failover retry happens too quickly when new leader suggested

[jira] [Commented] (HDDS-3354) OM HA replay optimization

[ https://issues.apache.org/jira/browse/HDDS-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093754#comment-17093754 ] Bharat Viswanadham commented on HDDS-3354: -- Hi [~elek] Thanks for reviewing design doc.

[jira] [Resolved] (HDDS-3467) OM Client RPC failover retries happening more than configured.

[ https://issues.apache.org/jira/browse/HDDS-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3467. -- Resolution: Fixed > OM Client RPC failover retries happening more than configured. >

[jira] [Updated] (HDDS-3393) Recon throws NPE in clusterState endpoint

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

[jira] [Assigned] (HDDS-3476) Use persisted transaction info during OM startup in OM StateMachine

[ https://issues.apache.org/jira/browse/HDDS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3476: Assignee: Bharat Viswanadham > Use persisted transaction info during OM startup in

[jira] [Updated] (HDDS-3475) Use transactionInfo table to persist transaction information

[ https://issues.apache.org/jira/browse/HDDS-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3475: - Status: Patch Available (was: Open) > Use transactionInfo table to persist transaction

[jira] [Updated] (HDDS-3354) OM HA replay optimization

[ https://issues.apache.org/jira/browse/HDDS-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3354: - Issue Type: Improvement (was: Bug) > OM HA replay optimization >

[jira] [Updated] (HDDS-3476) Use persisted transaction info during OM startup in OM StateMachine

[ https://issues.apache.org/jira/browse/HDDS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3476: - Parent: HDDS-3354 Issue Type: Sub-task (was: Bug) > Use persisted transaction

[jira] [Updated] (HDDS-3476) Use persisted transaction info during OM startup in OM StateMachine

[ https://issues.apache.org/jira/browse/HDDS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3476: - Description: HDDS-3475 persisted transaction info into DB. This Jira is to use

[jira] [Created] (HDDS-3476) Use persisted transaction info during OM startup in OM StateMachine

Bharat Viswanadham created HDDS-3476: Summary: Use persisted transaction info during OM startup in OM StateMachine Key: HDDS-3476 URL: https://issues.apache.org/jira/browse/HDDS-3476 Project:

[jira] [Created] (HDDS-3475) Use transactionInfo table to persist transaction information

Bharat Viswanadham created HDDS-3475: Summary: Use transactionInfo table to persist transaction information Key: HDDS-3475 URL: https://issues.apache.org/jira/browse/HDDS-3475 Project: Hadoop

[jira] [Updated] (HDDS-3474) Create transactionInfo Table in OmMetadataManager

[ https://issues.apache.org/jira/browse/HDDS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3474: - Status: Patch Available (was: In Progress) > Create transactionInfo Table in

[jira] [Assigned] (HDDS-3474) Create transactionInfo Table in OmMetadataManager

[ https://issues.apache.org/jira/browse/HDDS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3474: Assignee: Bharat Viswanadham > Create transactionInfo Table in OmMetadataManager >

[jira] [Created] (HDDS-3474) Create transactionInfo Table in OmMetadataManager

Bharat Viswanadham created HDDS-3474: Summary: Create transactionInfo Table in OmMetadataManager Key: HDDS-3474 URL: https://issues.apache.org/jira/browse/HDDS-3474 Project: Hadoop Distributed

[jira] [Updated] (HDDS-3465) OM Failover retry happens too quickly when new leader suggested and retrying on same OM

[ https://issues.apache.org/jira/browse/HDDS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3465: - Target Version/s: 0.6.0 > OM Failover retry happens too quickly when new leader suggested

[jira] [Updated] (HDDS-3465) OM Failover retry happens too quickly when new leader suggested and retrying on same OM

[ https://issues.apache.org/jira/browse/HDDS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3465: - Priority: Blocker (was: Major) > OM Failover retry happens too quickly when new leader

[jira] [Updated] (HDDS-3456) Fix Acceptance test failures due to disk out of space.

[ https://issues.apache.org/jira/browse/HDDS-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3456: - Summary: Fix Acceptance test failures due to disk out of space. (was: Acceptance test

[jira] [Updated] (HDDS-3456) Fix Acceptance test failures due to disk out of space.

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

[jira] [Resolved] (HDDS-1746) Allocating Blocks is not happening for Multipart upload part key in createMultipartKey call

[ https://issues.apache.org/jira/browse/HDDS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-1746. -- Resolution: Won't Fix This issue will be fixed once we have a strong leader guarantee

[jira] [Assigned] (HDDS-1892) HA failover attempt log level should be set to DEBUG

[ https://issues.apache.org/jira/browse/HDDS-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-1892: Assignee: Hanisha Koneru (was: Siyao Meng) > HA failover attempt log level should

[jira] [Resolved] (HDDS-1892) HA failover attempt log level should be set to DEBUG

[ https://issues.apache.org/jira/browse/HDDS-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-1892. -- Fix Version/s: 0.6.0 Resolution: Duplicate > HA failover attempt log level

[jira] [Resolved] (HDDS-2966) ACL checks should be done after acquiring lock

[ https://issues.apache.org/jira/browse/HDDS-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-2966. -- Resolution: Not A Problem > ACL checks should be done after acquiring lock >

[jira] [Commented] (HDDS-2966) ACL checks should be done after acquiring lock

[ https://issues.apache.org/jira/browse/HDDS-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086069#comment-17086069 ] Bharat Viswanadham commented on HDDS-2966: -- Closing this as it is not a problem, we acquire read

[jira] [Resolved] (HDDS-3322) StandAlone Pipelines are created in an infinite loop

[ https://issues.apache.org/jira/browse/HDDS-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3322. -- Fix Version/s: 0.6.0 Resolution: Fixed > StandAlone Pipelines are created in an

[jira] [Resolved] (HDDS-3401) Ozone audit entries could be consistent among volume creation with quota and update quota

[ https://issues.apache.org/jira/browse/HDDS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3401. -- Fix Version/s: 0.6.0 Resolution: Fixed > Ozone audit entries could be consistent

[jira] [Created] (HDDS-3408) Rename ChunkLayOutVersion -> ContainerLayOutVersion

Bharat Viswanadham created HDDS-3408: Summary: Rename ChunkLayOutVersion -> ContainerLayOutVersion Key: HDDS-3408 URL: https://issues.apache.org/jira/browse/HDDS-3408 Project: Hadoop Distributed

[jira] [Assigned] (HDDS-3408) Rename ChunkLayOutVersion -> ContainerLayOutVersion

[ https://issues.apache.org/jira/browse/HDDS-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3408: Assignee: Bharat Viswanadham > Rename ChunkLayOutVersion -> ContainerLayOutVersion

[jira] [Updated] (HDDS-3407) Reduce number of parameters in prepareKeyInfo in OMKeyRequest

[ https://issues.apache.org/jira/browse/HDDS-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3407: - Issue Type: Improvement (was: Bug) Priority: Minor (was: Major) > Reduce number

[jira] [Updated] (HDDS-3407) Reduce number of parameters in prepareKeyInfo in OMKeyRequest

[ https://issues.apache.org/jira/browse/HDDS-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3407: - Description: https://github.com/apache/hadoop-ozone/pull/830#discussion_r409733651 As

[jira] [Created] (HDDS-3407) Reduce number of parameters in prepareKeyInfo in OMKeyRequest

Bharat Viswanadham created HDDS-3407: Summary: Reduce number of parameters in prepareKeyInfo in OMKeyRequest Key: HDDS-3407 URL: https://issues.apache.org/jira/browse/HDDS-3407 Project: Hadoop

[jira] [Resolved] (HDDS-3291) Write operation when both OM followers are shutdown

[ https://issues.apache.org/jira/browse/HDDS-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3291. -- Resolution: Fixed > Write operation when both OM followers are shutdown >

[jira] [Updated] (HDDS-3401) Ozone audit entries could be consistent among volume creation with quota and update quota

[ https://issues.apache.org/jira/browse/HDDS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3401: - Priority: Minor (was: Major) > Ozone audit entries could be consistent among volume

[jira] [Created] (HDDS-3402) Use proper acls for sub directories created during CreateDirectory operation

Bharat Viswanadham created HDDS-3402: Summary: Use proper acls for sub directories created during CreateDirectory operation Key: HDDS-3402 URL: https://issues.apache.org/jira/browse/HDDS-3402

[jira] [Assigned] (HDDS-3401) Ozone audit entries could be consistent among volume creation with quota and update quota

[ https://issues.apache.org/jira/browse/HDDS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3401: Assignee: Bharat Viswanadham > Ozone audit entries could be consistent among

[jira] [Updated] (HDDS-3394) Skip generation of encryptionkey for directory create operation

[ https://issues.apache.org/jira/browse/HDDS-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3394: - Fix Version/s: (was: 0.5.0) 0.6.0 > Skip generation of

[jira] [Resolved] (HDDS-3394) Skip generation of encryptionkey for directory create operation

[ https://issues.apache.org/jira/browse/HDDS-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3394. -- Fix Version/s: 0.5.0 Resolution: Fixed > Skip generation of encryptionkey for

[jira] [Created] (HDDS-3394) Skip generation of encryptionkey for directory create operation

Bharat Viswanadham created HDDS-3394: Summary: Skip generation of encryptionkey for directory create operation Key: HDDS-3394 URL: https://issues.apache.org/jira/browse/HDDS-3394 Project: Hadoop

[jira] [Comment Edited] (HDDS-3378) OzoneManager group init failed because of incorrect snapshot directory location

[ https://issues.apache.org/jira/browse/HDDS-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082477#comment-17082477 ] Bharat Viswanadham edited comment on HDDS-3378 at 4/13/20, 4:48 PM: I

[jira] [Commented] (HDDS-3378) OzoneManager group init failed because of incorrect snapshot directory location

[ https://issues.apache.org/jira/browse/HDDS-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082477#comment-17082477 ] Bharat Viswanadham commented on HDDS-3378: -- I see this is happening because

[jira] [Assigned] (HDDS-3381) OzoneManager starts 2 OzoneManagerDoubleBuffer for HA clusters

[ https://issues.apache.org/jira/browse/HDDS-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3381: Assignee: Bharat Viswanadham > OzoneManager starts 2 OzoneManagerDoubleBuffer for

[jira] [Updated] (HDDS-3368) Ozone filesystem jar should not include webapps folder

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

[jira] [Reopened] (HDDS-3291) Write operation when both OM followers are shutdown

[ https://issues.apache.org/jira/browse/HDDS-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reopened HDDS-3291: -- This has been reverted, as this is causing an issue for Hadoop applications. > Write

[jira] [Updated] (HDDS-3375) S3A failing complete multipart upload with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3375: - Status: Patch Available (was: Open) > S3A failing complete multipart upload with Ozone

[jira] [Resolved] (HDDS-3372) Delete HISTORY.txt

[ https://issues.apache.org/jira/browse/HDDS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3372. -- Fix Version/s: 0.6.0 Resolution: Fixed > Delete HISTORY.txt > --

[jira] [Created] (HDDS-3375) S3A failing complete multipart upload with Ozone S3

Bharat Viswanadham created HDDS-3375: Summary: S3A failing complete multipart upload with Ozone S3 Key: HDDS-3375 URL: https://issues.apache.org/jira/browse/HDDS-3375 Project: Hadoop Distributed

[jira] [Resolved] (HDDS-3365) Ensure OzoneConfiguration is initialized in OzoneClientFactory#getOzoneClient

[ https://issues.apache.org/jira/browse/HDDS-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3365. -- Fix Version/s: 0.6.0 Resolution: Fixed > Ensure OzoneConfiguration is

[jira] [Updated] (HDDS-3217) Datanode startup is slow due to iterating container DB 2-3 times

[ https://issues.apache.org/jira/browse/HDDS-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3217: - Attachment: Datanode restart problem.pdf > Datanode startup is slow due to iterating

[jira] [Updated] (HDDS-3217) Datanode startup is slow due to iterating container DB 2-3 times

[ https://issues.apache.org/jira/browse/HDDS-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3217: - Issue Type: Improvement (was: Bug) Priority: Blocker (was: Critical) > Datanode

[jira] [Updated] (HDDS-3354) OM HA replay optimization

[ https://issues.apache.org/jira/browse/HDDS-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3354: - Attachment: OM HA Replay.pdf > OM HA replay optimization > - > >

[jira] [Created] (HDDS-3354) OM HA replay optimization

Bharat Viswanadham created HDDS-3354: Summary: OM HA replay optimization Key: HDDS-3354 URL: https://issues.apache.org/jira/browse/HDDS-3354 Project: Hadoop Distributed Data Store Issue

[jira] [Updated] (HDDS-3217) Datanode startup is slow due to iterating container DB 2-3 times

[ https://issues.apache.org/jira/browse/HDDS-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3217: - Status: Patch Available (was: In Progress) > Datanode startup is slow due to iterating

[jira] [Resolved] (HDDS-3344) Remove Jenkins file

[ https://issues.apache.org/jira/browse/HDDS-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3344. -- Fix Version/s: 0.6.0 Resolution: Fixed > Remove Jenkins file >

[jira] [Assigned] (HDDS-3351) Remove unnecessary dependency Curator

[ https://issues.apache.org/jira/browse/HDDS-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3351: Assignee: Istvan Fajth > Remove unnecessary dependency Curator >

[jira] [Resolved] (HDDS-3351) Remove unnecessary dependency Curator

[ https://issues.apache.org/jira/browse/HDDS-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3351. -- Fix Version/s: 0.6.0 Resolution: Fixed > Remove unnecessary dependency Curator >

[jira] [Commented] (HDDS-2353) Cleanup old write-path code in OM

[ https://issues.apache.org/jira/browse/HDDS-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075710#comment-17075710 ] Bharat Viswanadham commented on HDDS-2353: -- Hi [~cxorm] Thank You for the interest. I completely

[jira] [Assigned] (HDDS-2353) Cleanup old write-path code in OM

[ https://issues.apache.org/jira/browse/HDDS-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-2353: Assignee: YiSheng Lien (was: Bharat Viswanadham) > Cleanup old write-path code in

[jira] [Updated] (HDDS-3325) Handle Resource Unavailable exception in OM HA

[ https://issues.apache.org/jira/browse/HDDS-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3325: - Description: Right now, when the future fails with an exception, we send that exception

[jira] [Assigned] (HDDS-3325) Handle Resource Unavailable exception in OM HA

[ https://issues.apache.org/jira/browse/HDDS-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3325: Assignee: Bharat Viswanadham > Handle Resource Unavailable exception in OM HA >

[jira] [Resolved] (HDDS-3291) Write operation when both OM followers are shutdown

[ https://issues.apache.org/jira/browse/HDDS-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3291. -- Fix Version/s: 0.6.0 Resolution: Fixed > Write operation when both OM followers

[jira] [Resolved] (HDDS-3273) OM HA: getconf must return all OMs

[ https://issues.apache.org/jira/browse/HDDS-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3273. -- Fix Version/s: 0.6.0 Resolution: Fixed > OM HA: getconf must return all OMs >

<    1   2   3   4   5   6   7   8   >