[jira] [Assigned] (HDDS-3412) Ozone shell should have commands to delete non-empty volumes / buckets recursively

[ https://issues.apache.org/jira/browse/HDDS-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh reassigned HDDS-3412: --- Assignee: Sadanand Shenoy > Ozone shell should have commands to delete non-empty

[jira] [Created] (HDDS-3412) Ozone shell should have commands to delete non-empty volumes / buckets recursively

Gaurav created HDDS-3412: Summary: Ozone shell should have commands to delete non-empty volumes / buckets recursively Key: HDDS-3412 URL: https://issues.apache.org/jira/browse/HDDS-3412 Project: Hadoop

[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

[GitHub] [hadoop-ozone] bharatviswa504 commented on issue #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop

bharatviswa504 commented on issue #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop URL: https://github.com/apache/hadoop-ozone/pull/749#issuecomment-615032101 Thank You @hanishakoneru for the contribution and @vivekratnavel for the review.

[GitHub] [hadoop-ozone] bharatviswa504 merged pull request #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop

bharatviswa504 merged pull request #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop URL: https://github.com/apache/hadoop-ozone/pull/749 This is an automated message from the Apache Git Service. To

[GitHub] [hadoop-ozone] swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby.

swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby. URL: https://github.com/apache/hadoop-ozone/pull/839#discussion_r409983094 ## File path:

[GitHub] [hadoop-ozone] swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby.

swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby. URL: https://github.com/apache/hadoop-ozone/pull/839#discussion_r409983094 ## File path:

[GitHub] [hadoop-ozone] swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby.

swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby. URL: https://github.com/apache/hadoop-ozone/pull/839#discussion_r409983094 ## File path:

[GitHub] [hadoop-ozone] swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby.

swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby. URL: https://github.com/apache/hadoop-ozone/pull/839#discussion_r409982061 ## File path: hadoop-ozone/recon-codegen/src/main/java/org/hadoop/ozone/recon/codegen/JooqCodeGenerator.java

[GitHub] [hadoop-ozone] swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby.

swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby. URL: https://github.com/apache/hadoop-ozone/pull/839#discussion_r409982227 ## File path: hadoop-ozone/recon-codegen/src/main/java/org/hadoop/ozone/recon/codegen/JooqCodeGenerator.java

[GitHub] [hadoop-ozone] swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby.

swagle commented on a change in pull request #839: HDDS-3411. Switch Recon SQL DB to Derby. URL: https://github.com/apache/hadoop-ozone/pull/839#discussion_r409981449 ## File path: hadoop-ozone/recon-codegen/src/main/java/org/hadoop/ozone/recon/codegen/ReconSqlDbConfig.java

[jira] [Updated] (HDDS-3223) Read a big object is too slow by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Description: *What's the problem ?* Read a 300M file, it cost about 25 seconds, i.e. 12M/s, which is too

[jira] [Commented] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085414#comment-17085414 ] runzhiwang commented on HDDS-3223: -- I‘m working on it > Read a big object is slower than write it by s3g

[jira] [Updated] (HDDS-3223) Read a big object is too slow by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Summary: Read a big object is too slow by s3g (was: Read a big object is slower than write it by s3g) >

[jira] [Updated] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Description: *What's the problem ?* Read a 300M file, it cost about 25 seconds, i.e. 12.8M/s, which is

[GitHub] [hadoop-ozone] xiaoyuyao commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes

xiaoyuyao commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes URL: https://github.com/apache/hadoop-ozone/pull/696#discussion_r409977210 ## File path:

[jira] [Updated] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Attachment: screenshot-1.png > Read a big object is slower than write it by s3g >

[jira] [Reopened] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reopened HDDS-3223: -- > Read a big object is slower than write it by s3g > > >

[jira] [Updated] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Description: !screenshot-1.png! > Read a big object is slower than write it by s3g >

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Description: (was: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. Both

[jira] [Updated] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Attachment: (was: screenshot-5.png) > Read a big object is slower than write it by s3g >

[jira] [Issue Comment Deleted] (HDDS-3223) Read a big object cost 2 times more than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Comment: was deleted (was: I think it's related to our own operating system.) > Read a big object cost 2

[jira] [Updated] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Summary: Read a big object is slower than write it by s3g (was: Read a big object cost 2 times more than

[jira] [Updated] (HDDS-3223) Read a big object is slower than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Attachment: (was: screenshot-3.png) > Read a big object is slower than write it by s3g >

[jira] [Updated] (HDDS-3411) Switch Recon SQL DB to Derby.

[ https://issues.apache.org/jira/browse/HDDS-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3411: - Labels: pull-request-available (was: ) > Switch Recon SQL DB to Derby. >

[GitHub] [hadoop-ozone] avijayanhwx opened a new pull request #839: HDDS-3411. Switch Recon SQL DB to Derby.

avijayanhwx opened a new pull request #839: HDDS-3411. Switch Recon SQL DB to Derby. URL: https://github.com/apache/hadoop-ozone/pull/839 ## What changes were proposed in this pull request? Recon currently uses Sqlite as its defacto SQL DB with an option to configure other JDBC

[jira] [Created] (HDDS-3411) Switch Recon SQL DB to Derby.

Aravindan Vijayan created HDDS-3411: --- Summary: Switch Recon SQL DB to Derby. Key: HDDS-3411 URL: https://issues.apache.org/jira/browse/HDDS-3411 Project: Hadoop Distributed Data Store

[GitHub] [hadoop-ozone] maobaolong commented on issue #825: HDDS-3395. Move the protobuf convert code to the OMHelper

maobaolong commented on issue #825: HDDS-3395. Move the protobuf convert code to the OMHelper URL: https://github.com/apache/hadoop-ozone/pull/825#issuecomment-615009528 @bharatviswa504 Thank you for your review and your reply. There are the reasons why i did this moving. - If I

[jira] [Updated] (HDDS-3406) Remove RetryInvocation INFO logging from ozone CLI output

[ https://issues.apache.org/jira/browse/HDDS-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3406: - Labels: pull-request-available (was: ) > Remove RetryInvocation INFO logging from ozone CLI

[GitHub] [hadoop-ozone] hanishakoneru opened a new pull request #838: HDDS-3406. Remove RetryInvocation INFO logging from ozone CLI output

hanishakoneru opened a new pull request #838: HDDS-3406. Remove RetryInvocation INFO logging from ozone CLI output URL: https://github.com/apache/hadoop-ozone/pull/838 ## What changes were proposed in this pull request? In OM HA failover proxy provider, RetryInvocationHandler logs

[GitHub] [hadoop-ozone] smengcl commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes

smengcl commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes URL: https://github.com/apache/hadoop-ozone/pull/696#discussion_r409905641 ## File path:

[GitHub] [hadoop-ozone] smengcl commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes

smengcl commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes URL: https://github.com/apache/hadoop-ozone/pull/696#discussion_r409897810 ## File path:

[GitHub] [hadoop-ozone] smengcl commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes

smengcl commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes URL: https://github.com/apache/hadoop-ozone/pull/696#discussion_r409897865 ## File path:

[GitHub] [hadoop-ozone] bharatviswa504 edited a comment on issue #825: HDDS-3395. Move the protobuf convert code to the OMHelper

bharatviswa504 edited a comment on issue #825: HDDS-3395. Move the protobuf convert code to the OMHelper URL: https://github.com/apache/hadoop-ozone/pull/825#issuecomment-614930795 I believe instead of moving proto conversions into OMPBHelper, I believe the current approach of each Class

[GitHub] [hadoop-ozone] bharatviswa504 commented on issue #825: HDDS-3395. Move the protobuf convert code to the OMHelper

bharatviswa504 commented on issue #825: HDDS-3395. Move the protobuf convert code to the OMHelper URL: https://github.com/apache/hadoop-ozone/pull/825#issuecomment-614930795 I believe instead of moving this in to OMPBHelper, I believe current approach of Each Class having the logic of

[GitHub] [hadoop-ozone] bharatviswa504 commented on a change in pull request #833: HDDS-3314. scmcli container info command failing intermittently

bharatviswa504 commented on a change in pull request #833: HDDS-3314. scmcli container info command failing intermittently URL: https://github.com/apache/hadoop-ozone/pull/833#discussion_r409885190 ## File path:

[GitHub] [hadoop-ozone] bharatviswa504 commented on a change in pull request #833: HDDS-3314. scmcli container info command failing intermittently

bharatviswa504 commented on a change in pull request #833: HDDS-3314. scmcli container info command failing intermittently URL: https://github.com/apache/hadoop-ozone/pull/833#discussion_r409885190 ## File path:

[jira] [Updated] (HDDS-3409) Update download links

[ https://issues.apache.org/jira/browse/HDDS-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-3409: Description: The download links for signatures/checksums/KEYS should be updated from

[jira] [Created] (HDDS-3410) Update download links

Arpit Agarwal created HDDS-3410: --- Summary: Update download links Key: HDDS-3410 URL: https://issues.apache.org/jira/browse/HDDS-3410 Project: Hadoop Distributed Data Store Issue Type:

[jira] [Moved] (HDDS-3409) Update download links

[ https://issues.apache.org/jira/browse/HDDS-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal moved HADOOP-16992 to HDDS-3409: -- Component/s: (was: website) website

[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] [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 ] ASF GitHub Bot updated HDDS-3401: - Labels: pull-request-available (was: ) > Ozone audit entries could be consistent among volume

[GitHub] [hadoop-ozone] bharatviswa504 commented on issue #832: HDDS-3401. Ozone audit entries could be consistent among volume creation with quota and update quota

bharatviswa504 commented on issue #832: HDDS-3401. Ozone audit entries could be consistent among volume creation with quota and update quota URL: https://github.com/apache/hadoop-ozone/pull/832#issuecomment-614920215 Thank You @arp7 for the review.

[GitHub] [hadoop-ozone] bharatviswa504 merged pull request #832: HDDS-3401. Ozone audit entries could be consistent among volume creation with quota and update quota

bharatviswa504 merged pull request #832: HDDS-3401. Ozone audit entries could be consistent among volume creation with quota and update quota URL: https://github.com/apache/hadoop-ozone/pull/832 This is an automated message

[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

[GitHub] [hadoop-ozone] bharatviswa504 commented on issue #742: HDDS-3217. Datanode startup is slow due to iterating container DB 2-3 times.

bharatviswa504 commented on issue #742: HDDS-3217. Datanode startup is slow due to iterating container DB 2-3 times. URL: https://github.com/apache/hadoop-ozone/pull/742#issuecomment-614904094 Thank You @bshashikant for the review. Added code changes to handle upgrade. This is brought

[GitHub] [hadoop-ozone] xiaoyuyao commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes

xiaoyuyao commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes URL: https://github.com/apache/hadoop-ozone/pull/696#discussion_r409834931 ## File path:

[GitHub] [hadoop-ozone] xiaoyuyao commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes

xiaoyuyao commented on a change in pull request #696: HDDS-3056. Allow users to list volumes they have access to, and optionally allow all users to list all volumes URL: https://github.com/apache/hadoop-ozone/pull/696#discussion_r409833261 ## File path:

[jira] [Resolved] (HDDS-3392) OM create key/file should not generate different data encryption key during validateAndUpdateCache

[ https://issues.apache.org/jira/browse/HDDS-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal resolved HDDS-3392. - Fix Version/s: 0.6.0 Target Version/s: (was: 0.6.0) Resolution: Fixed > OM

[GitHub] [hadoop-ozone] bharatviswa504 merged pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

bharatviswa504 merged pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830 This is an

[GitHub] [hadoop-ozone] bharatviswa504 commented on issue #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

bharatviswa504 commented on issue #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830#issuecomment-614852947 Thank You @xiaoyuyao for the review.

[GitHub] [hadoop-ozone] xiaoyuyao commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

xiaoyuyao commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830#discussion_r409799258 ## File path:

[GitHub] [hadoop-ozone] bharatviswa504 commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

bharatviswa504 commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830#discussion_r409798023 ## File path:

[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

[GitHub] [hadoop-ozone] bharatviswa504 commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

bharatviswa504 commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830#discussion_r409792436 ## File path:

[GitHub] [hadoop-ozone] bharatviswa504 commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

bharatviswa504 commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830#discussion_r409791272 ## File path:

[jira] [Commented] (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:comment-tabpanel=17085190#comment-17085190 ] Arpit Agarwal commented on HDDS-3291: - This was re-committed via GitHub PR #815. > Write operation

[GitHub] [hadoop-ozone] prashantpogde commented on issue #828: HDDS-3002. NFS mountd support for Ozone

prashantpogde commented on issue #828: HDDS-3002. NFS mountd support for Ozone URL: https://github.com/apache/hadoop-ozone/pull/828#issuecomment-614834393 yup @mukul1987, looking at failures and fixing them. I will upload another patch.

[GitHub] [hadoop-ozone] adoroszlai opened a new pull request #837: HDDS-3400. Extract test utilities to separate module

adoroszlai opened a new pull request #837: HDDS-3400. Extract test utilities to separate module URL: https://github.com/apache/hadoop-ozone/pull/837 ## What changes were proposed in this pull request? Create `hadoop-hdds/test-utils` module for test utilities (eg. `GenericTestUtils`

[jira] [Updated] (HDDS-3400) Extract test utilities to separate module

[ https://issues.apache.org/jira/browse/HDDS-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3400: - Labels: pull-request-available (was: ) > Extract test utilities to separate module >

[jira] [Commented] (HDDS-3406) Remove RetryInvocation INFO logging from ozone CLI output

[ https://issues.apache.org/jira/browse/HDDS-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085181#comment-17085181 ] Hanisha Koneru commented on HDDS-3406: -- Thanks [~ayushtkn]. Added to Common by mistake. > Remove

[jira] [Updated] (HDDS-3406) Remove RetryInvocation INFO logging from ozone CLI output

[ https://issues.apache.org/jira/browse/HDDS-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDDS-3406: - Description: In OM HA failover proxy provider, RetryInvocationHandler logs error stack trace

[jira] [Updated] (HDDS-3406) Remove RetryInvocation INFO logging from ozone CLI output

[ https://issues.apache.org/jira/browse/HDDS-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDDS-3406: - Component/s: Ozone Client om > Remove RetryInvocation INFO logging from ozone

[jira] [Updated] (HDDS-3406) Remove RetryInvocation INFO logging from ozone CLI output

[ https://issues.apache.org/jira/browse/HDDS-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDDS-3406: - Description: In OM HA failover proxy provider, RetryInvocationHandler logs error stack trace

[jira] [Commented] (HDDS-3406) Remove RetryInvocation INFO logging from ozone CLI output

[ https://issues.apache.org/jira/browse/HDDS-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085179#comment-17085179 ] Ayush Saxena commented on HDDS-3406: Seems Not related to Common, Have moved from Common to HDDS. >

[jira] [Moved] (HDDS-3406) Remove RetryInvocation INFO logging from ozone CLI output

[ https://issues.apache.org/jira/browse/HDDS-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena moved HADOOP-16991 to HDDS-3406: - Key: HDDS-3406 (was: HADOOP-16991) Target Version/s:

[GitHub] [hadoop-ozone] xiaoyuyao commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

xiaoyuyao commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830#discussion_r409734021 ## File path:

[GitHub] [hadoop-ozone] xiaoyuyao commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache.

xiaoyuyao commented on a change in pull request #830: HDDS-3392.OM create key/file should not generate different data encryption key during validateAndUpdateCache. URL: https://github.com/apache/hadoop-ozone/pull/830#discussion_r409733651 ## File path:

[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 >

[GitHub] [hadoop-ozone] bharatviswa504 commented on issue #815: HDDS-3291. Write operation when both OM followers are shutdown.

bharatviswa504 commented on issue #815: HDDS-3291. Write operation when both OM followers are shutdown. URL: https://github.com/apache/hadoop-ozone/pull/815#issuecomment-614785352 Thank You @arp7 for the review. This is an

[GitHub] [hadoop-ozone] bharatviswa504 merged pull request #815: HDDS-3291. Write operation when both OM followers are shutdown.

bharatviswa504 merged pull request #815: HDDS-3291. Write operation when both OM followers are shutdown. URL: https://github.com/apache/hadoop-ozone/pull/815 This is an automated message from the Apache Git Service. To

[GitHub] [hadoop-ozone] nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM

nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM URL: https://github.com/apache/hadoop-ozone/pull/700#discussion_r409710625 ## File path:

[GitHub] [hadoop-ozone] nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM

nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM URL: https://github.com/apache/hadoop-ozone/pull/700#discussion_r409716835 ## File path:

[GitHub] [hadoop-ozone] nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM

nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM URL: https://github.com/apache/hadoop-ozone/pull/700#discussion_r409716530 ## File path:

[GitHub] [hadoop-ozone] nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM

nandakumar131 commented on a change in pull request #700: HDDS-3172. Use DBStore instead of MetadataStore in SCM URL: https://github.com/apache/hadoop-ozone/pull/700#discussion_r409718432 ## File path:

[jira] [Updated] (HDDS-3172) Use DBStore instead of MetadataStore in SCM

[ https://issues.apache.org/jira/browse/HDDS-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-3172: -- Status: Patch Available (was: Open) > Use DBStore instead of MetadataStore in SCM >

[jira] [Updated] (HDDS-3172) Use DBStore instead of MetadataStore in SCM

[ https://issues.apache.org/jira/browse/HDDS-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-3172: -- Labels: backward-incompatible pull-request-available (was: pull-request-available) > Use DBStore

[GitHub] [hadoop-ozone] hanishakoneru commented on issue #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop

hanishakoneru commented on issue #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop URL: https://github.com/apache/hadoop-ozone/pull/749#issuecomment-614744200 Thanks @bharatviswa504 and @vivekratnavel for the reviews. > One question, so you have tested the

[GitHub] [hadoop-ozone] hanishakoneru commented on a change in pull request #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop

hanishakoneru commented on a change in pull request #749: HDDS-3322. StandAlone Pipelines are created in an infinite loop URL: https://github.com/apache/hadoop-ozone/pull/749#discussion_r409672521 ## File path:

[jira] [Resolved] (HDDS-3364) Increase test timeout for ozonesecure-security robot tests

[ https://issues.apache.org/jira/browse/HDDS-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru resolved HDDS-3364. -- Resolution: Not A Problem > Increase test timeout for ozonesecure-security robot tests >

[GitHub] [hadoop-ozone] hanishakoneru closed pull request #791: HDDS-3364. Increase test timeout for ozonesecure-security robot tests

hanishakoneru closed pull request #791: HDDS-3364. Increase test timeout for ozonesecure-security robot tests URL: https://github.com/apache/hadoop-ozone/pull/791 This is an automated message from the Apache Git Service. To

[GitHub] [hadoop-ozone] hanishakoneru commented on issue #791: HDDS-3364. Increase test timeout for ozonesecure-security robot tests

hanishakoneru commented on issue #791: HDDS-3364. Increase test timeout for ozonesecure-security robot tests URL: https://github.com/apache/hadoop-ozone/pull/791#issuecomment-614736236 Thank you @adoroszlai and @arp7 for the discussion. Closing this PR.

[jira] [Updated] (HDDS-3405) Tool for Listing keys in OpenKeyTable

[ https://issues.apache.org/jira/browse/HDDS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sadanand Shenoy updated HDDS-3405: -- Labels: (was: ozone) > Tool for Listing keys in OpenKeyTable >

[jira] [Updated] (HDDS-3403) Generate ozone specific version from type in FSProto.proto

[ https://issues.apache.org/jira/browse/HDDS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marton Elek updated HDDS-3403: -- Description: FSProtos.proto is copied from the Hadoop and used during the proto file generation

[GitHub] [hadoop-ozone] elek opened a new pull request #836: Hdds 3403

elek opened a new pull request #836: Hdds 3403 URL: https://github.com/apache/hadoop-ozone/pull/836 ## What changes were proposed in this pull request? FSProtos.proto is copied from the Hadoop and used during the proto file generation *BUT* the types defined in FSProtos.proto are

[jira] [Created] (HDDS-3405) Tool for Listing keys in OpenKeyTable

Sadanand Shenoy created HDDS-3405: - Summary: Tool for Listing keys in OpenKeyTable Key: HDDS-3405 URL: https://issues.apache.org/jira/browse/HDDS-3405 Project: Hadoop Distributed Data Store

[jira] [Assigned] (HDDS-3405) Tool for Listing keys in OpenKeyTable

[ https://issues.apache.org/jira/browse/HDDS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sadanand Shenoy reassigned HDDS-3405: - Assignee: Sadanand Shenoy > Tool for Listing keys in OpenKeyTable >

[jira] [Updated] (HDDS-3399) Update JaegerTracing

[ https://issues.apache.org/jira/browse/HDDS-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3399: - Labels: pull-request-available (was: ) > Update JaegerTracing > > >

[GitHub] [hadoop-ozone] elek opened a new pull request #835: HDDS-3399. Update JaegerTracing

elek opened a new pull request #835: HDDS-3399. Update JaegerTracing URL: https://github.com/apache/hadoop-ozone/pull/835 ## What changes were proposed in this pull request? We currently use JaegerTracing 0.34.0. The latest is 1.2.0. We are several versions behind and should update.

[GitHub] [hadoop-ozone] adoroszlai commented on issue #818: HDDS-3386. Remove unnecessary transitive hadoop-common dependencies on server side (addendum).

adoroszlai commented on issue #818: HDDS-3386. Remove unnecessary transitive hadoop-common dependencies on server side (addendum). URL: https://github.com/apache/hadoop-ozone/pull/818#issuecomment-614661190 Sorry, I should have triggered CI here, since unfortunately my PR was merged

[jira] [Updated] (HDDS-3404) Fix TestDnRatisLogParser

[ https://issues.apache.org/jira/browse/HDDS-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-3404: -- Attachment: it-ozone.zip > Fix TestDnRatisLogParser > > >

[jira] [Created] (HDDS-3404) Fix TestDnRatisLogParser

Shashikant Banerjee created HDDS-3404: - Summary: Fix TestDnRatisLogParser Key: HDDS-3404 URL: https://issues.apache.org/jira/browse/HDDS-3404 Project: Hadoop Distributed Data Store Issue

[GitHub] [hadoop-ozone] bshashikant commented on a change in pull request #716: HDDS-3155. Improved ozone client flush implementation to make it faster.

bshashikant commented on a change in pull request #716: HDDS-3155. Improved ozone client flush implementation to make it faster. URL: https://github.com/apache/hadoop-ozone/pull/716#discussion_r409558243 ## File path:

[jira] [Resolved] (HDDS-3386) Remove unnecessary transitive hadoop-common dependencies on server side (addendum)

[ https://issues.apache.org/jira/browse/HDDS-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai resolved HDDS-3386. Fix Version/s: 0.6.0 Resolution: Fixed > Remove unnecessary transitive hadoop-common

[jira] [Updated] (HDDS-3386) Remove unnecessary transitive hadoop-common dependencies on server side (addendum)

[ https://issues.apache.org/jira/browse/HDDS-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai updated HDDS-3386: --- Labels: (was: pull-request-available) > Remove unnecessary transitive hadoop-common

[GitHub] [hadoop-ozone] adoroszlai commented on issue #818: HDDS-3386. Remove unnecessary transitive hadoop-common dependencies on server side (addendum).

adoroszlai commented on issue #818: HDDS-3386. Remove unnecessary transitive hadoop-common dependencies on server side (addendum). URL: https://github.com/apache/hadoop-ozone/pull/818#issuecomment-614650436 Thanks @fapifta for the contribution.

[GitHub] [hadoop-ozone] adoroszlai merged pull request #818: HDDS-3386. Remove unnecessary transitive hadoop-common dependencies on server side (addendum).

adoroszlai merged pull request #818: HDDS-3386. Remove unnecessary transitive hadoop-common dependencies on server side (addendum). URL: https://github.com/apache/hadoop-ozone/pull/818 This is an automated message from the

  1   2   >