[jira] [Updated] (HDDS-4405) Proxy failover is logging with out trying all OMS

[ https://issues.apache.org/jira/browse/HDDS-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4405: - Reporter: umamaheswararao (was: Bharat Viswanadham) > Proxy failover is logging with out

[jira] [Created] (HDDS-4405) Proxy failover is logging with out trying all OMS

Bharat Viswanadham created HDDS-4405: Summary: Proxy failover is logging with out trying all OMS Key: HDDS-4405 URL: https://issues.apache.org/jira/browse/HDDS-4405 Project: Hadoop Distributed

[jira] [Updated] (HDDS-4117) Normalize Keypath for listKeys.

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

[jira] [Resolved] (HDDS-3995) s3g met NPE exception while write file by multiPartUpload

[ https://issues.apache.org/jira/browse/HDDS-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3995. -- Fix Version/s: 1.1.0 Resolution: Fixed > s3g met NPE exception while write file

[jira] [Commented] (HDDS-4164) OM client request fails with "failed to commit as key is not found in OpenKey table"

[ https://issues.apache.org/jira/browse/HDDS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17214285#comment-17214285 ] Bharat Viswanadham commented on HDDS-4164: -- This issue is fixed by HDDS-4262. > OM client

[jira] [Commented] (HDDS-4164) OM client request fails with "failed to commit as key is not found in OpenKey table"

[ https://issues.apache.org/jira/browse/HDDS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17214284#comment-17214284 ] Bharat Viswanadham commented on HDDS-4164: -- Thank You, [~ljain] and [~weichiu] for the testing

[jira] [Resolved] (HDDS-4164) OM client request fails with "failed to commit as key is not found in OpenKey table"

[ https://issues.apache.org/jira/browse/HDDS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4164. -- Fix Version/s: 1.1.0 Resolution: Fixed > OM client request fails with "failed to

[jira] [Updated] (HDDS-4338) SCM web UI banner shows "HDFS SCM"

[ https://issues.apache.org/jira/browse/HDDS-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4338: - Labels: newbie (was: ) > SCM web UI banner shows "HDFS SCM" >

[jira] [Commented] (HDDS-4164) OM client request fails with "failed to commit as key is not found in OpenKey table"

[ https://issues.apache.org/jira/browse/HDDS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213347#comment-17213347 ] Bharat Viswanadham commented on HDDS-4164: -- Annotation of methods is just for representational

[jira] [Commented] (HDDS-4339) Ozone S3 gateway throws NPE with goofys

[ https://issues.apache.org/jira/browse/HDDS-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213335#comment-17213335 ] Bharat Viswanadham commented on HDDS-4339: -- This looks similar to HDDS-3843 where when auth

[jira] [Updated] (HDDS-4327) Potential resource leakage using BatchOperation

[ https://issues.apache.org/jira/browse/HDDS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4327: - Status: Patch Available (was: In Progress) > Potential resource leakage using

[jira] [Updated] (HDDS-4266) CreateFile : store parent dir entries into DirTable and file entry into separate FileTable

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

[jira] [Resolved] (HDDS-4122) Implement OM Delete Expired Open Key Request and Response

[ https://issues.apache.org/jira/browse/HDDS-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4122. -- Fix Version/s: 1.1.0 Resolution: Fixed > Implement OM Delete Expired Open Key

[jira] [Comment Edited] (HDDS-4339) Ozone S3 gateway throws NPE with goofys

[ https://issues.apache.org/jira/browse/HDDS-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213186#comment-17213186 ] Bharat Viswanadham edited comment on HDDS-4339 at 10/13/20, 3:46 PM: -  

[jira] [Commented] (HDDS-4339) Ozone S3 gateway throws NPE with goofys

[ https://issues.apache.org/jira/browse/HDDS-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213186#comment-17213186 ] Bharat Viswanadham commented on HDDS-4339: -- {quote}Export AWS secrets on the s3g host. See a

[jira] [Commented] (HDDS-4327) Potential resource leakage using BatchOperation

[ https://issues.apache.org/jira/browse/HDDS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212740#comment-17212740 ] Bharat Viswanadham commented on HDDS-4327: -- Thank You [~weichiu] for the catch. I will post a PR

[jira] [Commented] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212736#comment-17212736 ] Bharat Viswanadham commented on HDDS-4308: -- {quote}The performance impact of volume lock hasn’t

[jira] [Created] (HDDS-4329) Expose Ratis retry config cache in OM

Bharat Viswanadham created HDDS-4329: Summary: Expose Ratis retry config cache in OM Key: HDDS-4329 URL: https://issues.apache.org/jira/browse/HDDS-4329 Project: Hadoop Distributed Data Store

[jira] [Comment Edited] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211269#comment-17211269 ] Bharat Viswanadham edited comment on HDDS-4308 at 10/9/20, 6:47 PM:

[jira] [Commented] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211269#comment-17211269 ] Bharat Viswanadham commented on HDDS-4308: -- I think the better solution here is copy of a new

[jira] [Comment Edited] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211254#comment-17211254 ] Bharat Viswanadham edited comment on HDDS-4308 at 10/9/20, 6:17 PM: As

[jira] [Commented] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211254#comment-17211254 ] Bharat Viswanadham commented on HDDS-4308: -- As mentioned in the scenario this can happen when

[jira] [Commented] (HDDS-4164) OM client request fails with "failed to commit as key is not found in OpenKey table"

[ https://issues.apache.org/jira/browse/HDDS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211251#comment-17211251 ] Bharat Viswanadham commented on HDDS-4164: -- HDDS-4262 is the root cause for this issue, when

[jira] [Updated] (HDDS-4262) Use ClientID and CallID from Rpc Client to detect retry requests

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

[jira] [Commented] (HDDS-4327) Potential resource leakage using BatchOperation

[ https://issues.apache.org/jira/browse/HDDS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210393#comment-17210393 ] Bharat Viswanadham commented on HDDS-4327: -- [~weichiu] Are there any places in code you have

[jira] [Updated] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4308: - Description: Currently volumeArgs using getCacheValue and put the same object in

[jira] [Updated] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4308: - Description: Currently volumeArgs using getCacheValue and put the same object in

[jira] [Updated] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4308: - Description: Currently volumeArgs using getCacheValue and put the same object in

[jira] [Updated] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4308: - Priority: Blocker (was: Major) > Fix issue with quota update >

[jira] [Commented] (HDDS-4308) Fix issue with quota update

[ https://issues.apache.org/jira/browse/HDDS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208208#comment-17208208 ] Bharat Viswanadham commented on HDDS-4308: -- cc [~micahzhao] For ur comments on this issue. > Fix

[jira] [Created] (HDDS-4308) Fix issue with quota update

Bharat Viswanadham created HDDS-4308: Summary: Fix issue with quota update Key: HDDS-4308 URL: https://issues.apache.org/jira/browse/HDDS-4308 Project: Hadoop Distributed Data Store

[jira] [Assigned] (HDDS-3966) Intermittent crash in TestOMRatisSnapshots

[ https://issues.apache.org/jira/browse/HDDS-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3966: Assignee: Aryan Gupta > Intermittent crash in TestOMRatisSnapshots >

[jira] [Resolved] (HDDS-3966) Intermittent crash in TestOMRatisSnapshots

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

[jira] [Updated] (HDDS-2949) mkdir : store directory entries in a separate table

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

[jira] [Resolved] (HDDS-4251) Update Ratis version to latest snapshot

[ https://issues.apache.org/jira/browse/HDDS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4251. -- Fix Version/s: 1.1.0 Resolution: Fixed > Update Ratis version to latest snapshot

[jira] [Resolved] (HDDS-4292) Ozone Client not working with Hadoop Version < 3.2

[ https://issues.apache.org/jira/browse/HDDS-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4292. -- Fix Version/s: 1.1.0 Resolution: Fixed > Ozone Client not working with Hadoop

[jira] [Updated] (HDDS-4292) Ozone Client not working with Hadoop Version < 3.2

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

[jira] [Updated] (HDDS-4292) Ozone Client not working with Hadoop Version < 3.2

[ https://issues.apache.org/jira/browse/HDDS-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4292: - Summary: Ozone Client not working with Hadoop Version < 3.2 (was: Ozone Client not

[jira] [Updated] (HDDS-4292) Ozone Client not working with Hadoop Version < 3.2

[ https://issues.apache.org/jira/browse/HDDS-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4292: - Summary: Ozone Client not working with Hadoop Version < 3.2 (was:

[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: - Component/s: OM HA > Retry Cache in OM > - > > Key:

[jira] [Updated] (HDDS-4262) Use ClientID and CallID from Rpc Client to detect retry requests

[ https://issues.apache.org/jira/browse/HDDS-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4262: - Component/s: OM HA > Use ClientID and CallID from Rpc Client to detect retry requests >

[jira] [Updated] (HDDS-4262) Use ClientID and CallID from Rpc Client to detect retry requests

[ https://issues.apache.org/jira/browse/HDDS-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4262: - Affects Version/s: 1.0.0 > Use ClientID and CallID from Rpc Client to detect retry

[jira] [Updated] (HDDS-4262) Use ClientID and CallID from Rpc Client to detect retry requests

[ https://issues.apache.org/jira/browse/HDDS-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4262: - Environment: (was: U) > Use ClientID and CallID from Rpc Client to detect retry

[jira] [Updated] (HDDS-4262) Use ClientID and CallID from Rpc Client to detect retry requests

[ https://issues.apache.org/jira/browse/HDDS-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4262: - Status: Patch Available (was: Open) > Use ClientID and CallID from Rpc Client to detect

[jira] [Created] (HDDS-4262) Use ClientID and CallID from Rpc Client to detect retry requests

Bharat Viswanadham created HDDS-4262: Summary: Use ClientID and CallID from Rpc Client to detect retry requests Key: HDDS-4262 URL: https://issues.apache.org/jira/browse/HDDS-4262 Project: Hadoop

[jira] [Resolved] (HDDS-4248) Add ratis log parser to ozone script

[ https://issues.apache.org/jira/browse/HDDS-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4248. -- Resolution: Invalid > Add ratis log parser to ozone script >

[jira] [Resolved] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4210. -- Fix Version/s: 1.1.0 Resolution: Fixed > ResolveBucket during checkAcls fails >

[jira] [Assigned] (HDDS-4248) Add ratis log parser to ozone script

[ https://issues.apache.org/jira/browse/HDDS-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4248: Assignee: Bharat Viswanadham > Add ratis log parser to ozone script >

[jira] [Created] (HDDS-4248) Add ratis log parser to ozone script

Bharat Viswanadham created HDDS-4248: Summary: Add ratis log parser to ozone script Key: HDDS-4248 URL: https://issues.apache.org/jira/browse/HDDS-4248 Project: Hadoop Distributed Data Store

[jira] [Resolved] (HDDS-4075) Retry request on different OM on AccessControlException

[ https://issues.apache.org/jira/browse/HDDS-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4075. -- Fix Version/s: 1.1.0 Resolution: Fixed > Retry request on different OM on

[jira] [Commented] (HDDS-4243) Get API not working from S3A filesystem with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195782#comment-17195782 ] Bharat Viswanadham commented on HDDS-4243: -- With below config changes, able to read file from

[jira] [Assigned] (HDDS-4243) Get API not working from S3A filesystem with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4243: Assignee: Bharat Viswanadham > Get API not working from S3A filesystem with Ozone

[jira] [Updated] (HDDS-4243) Get API not working from S3A filesystem with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4243: - Component/s: S3 > Get API not working from S3A filesystem with Ozone S3 >

[jira] [Updated] (HDDS-4243) Get API not working from S3A filesystem with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4243: - Labels: OzoneS3 S3A (was: ) > Get API not working from S3A filesystem with Ozone S3 >

[jira] [Updated] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4209: - Labels: OzoneS3 S3A pull-request-available (was: pull-request-available) > S3A

[jira] [Created] (HDDS-4243) Get API not working from S3A filesystem with Ozone S3

Bharat Viswanadham created HDDS-4243: Summary: Get API not working from S3A filesystem with Ozone S3 Key: HDDS-4243 URL: https://issues.apache.org/jira/browse/HDDS-4243 Project: Hadoop Distributed

[jira] [Commented] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195679#comment-17195679 ] Bharat Viswanadham commented on HDDS-4155: -- [~elek] I have committed this, and only change takes

[jira] [Updated] (HDDS-4155) Directory and filename can end up with same name in a path

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

[jira] [Commented] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17194562#comment-17194562 ] Bharat Viswanadham commented on HDDS-4209: -- Posted a draft PR, when discussing with [~avijayan]

[jira] [Commented] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17194513#comment-17194513 ] Bharat Viswanadham commented on HDDS-4209: -- Looked in to S3A code, when directory path does not

[jira] [Comment Edited] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193033#comment-17193033 ] Bharat Viswanadham edited comment on HDDS-4209 at 9/11/20, 8:16 PM: Hi

[jira] [Comment Edited] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193033#comment-17193033 ] Bharat Viswanadham edited comment on HDDS-4209 at 9/9/20, 4:56 PM: --- Hi

[jira] [Commented] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193033#comment-17193033 ] Bharat Viswanadham commented on HDDS-4209: -- Hi [~elek] For your test have you enabled this

[jira] [Comment Edited] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192296#comment-17192296 ] Bharat Viswanadham edited comment on HDDS-4209 at 9/8/20, 4:09 PM: ---

[jira] [Commented] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192296#comment-17192296 ] Bharat Viswanadham commented on HDDS-4209: -- [~elek] I am not sure if this is the corner case.

[jira] [Comment Edited] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192296#comment-17192296 ] Bharat Viswanadham edited comment on HDDS-4209 at 9/8/20, 4:08 PM: ---

[jira] [Updated] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4210: - Target Version/s: 1.1.0 > ResolveBucket during checkAcls fails >

[jira] [Updated] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4210: - Description: In HA, in validateAndUpdateCache when resolveBucket, it checks the

[jira] [Updated] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4210: - Labels: (was: OzoneManager) > ResolveBucket during checkAcls fails >

[jira] [Updated] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4210: - Labels: OzoneManager (was: ) > ResolveBucket during checkAcls fails >

[jira] [Updated] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4210: - Component/s: Ozone Manager > ResolveBucket during checkAcls fails >

[jira] [Updated] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4210: - Priority: Blocker (was: Major) > ResolveBucket during checkAcls fails >

[jira] [Created] (HDDS-4210) ResolveBucket during checkAcls fails

Bharat Viswanadham created HDDS-4210: Summary: ResolveBucket during checkAcls fails Key: HDDS-4210 URL: https://issues.apache.org/jira/browse/HDDS-4210 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-4210) ResolveBucket during checkAcls fails

[ https://issues.apache.org/jira/browse/HDDS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4210: - Affects Version/s: 1.0.0 > ResolveBucket during checkAcls fails >

[jira] [Comment Edited] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190803#comment-17190803 ] Bharat Viswanadham edited comment on HDDS-4155 at 9/4/20, 4:05 PM: ---

[jira] [Comment Edited] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190803#comment-17190803 ] Bharat Viswanadham edited comment on HDDS-4155 at 9/4/20, 4:04 PM: ---

[jira] [Commented] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190803#comment-17190803 ] Bharat Viswanadham commented on HDDS-4155: -- {quote}I am wondering what is the problem with it. It

[jira] [Resolved] (HDDS-3077) Lost volume after changing access key

[ https://issues.apache.org/jira/browse/HDDS-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3077. -- Resolution: Invalid Now, this is not an issue, as we have removed the logic of to

[jira] [Commented] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190544#comment-17190544 ] Bharat Viswanadham commented on HDDS-4155: -- Yes, currently it can happen. This is because we

[jira] [Comment Edited] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190541#comment-17190541 ] Bharat Viswanadham edited comment on HDDS-4097 at 9/4/20, 5:00 AM: --- One

[jira] [Updated] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4209: - Priority: Blocker (was: Major) > S3A Filesystem does not work with Ozone S3 >

[jira] [Commented] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190541#comment-17190541 ] Bharat Viswanadham commented on HDDS-4097: -- One more interesting thing  HDDS-4029 S3A filesystem

[jira] [Commented] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190540#comment-17190540 ] Bharat Viswanadham commented on HDDS-4209: -- >From this looks like, we need to disable the flag

[jira] [Assigned] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4209: Assignee: Bharat Viswanadham > S3A Filesystem does not work with Ozone S3 >

[jira] [Updated] (HDDS-4209) S3A Filesystem does not work with Ozone S3

[ https://issues.apache.org/jira/browse/HDDS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4209: - Parent: HDDS-4097 Issue Type: Sub-task (was: Bug) > S3A Filesystem does not work

[jira] [Created] (HDDS-4209) S3A Filesystem does not work with Ozone S3

Bharat Viswanadham created HDDS-4209: Summary: S3A Filesystem does not work with Ozone S3 Key: HDDS-4209 URL: https://issues.apache.org/jira/browse/HDDS-4209 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-4121) Implement OmMetadataMangerImpl#getExpiredOpenKeys

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

[jira] [Resolved] (HDDS-4121) Implement OmMetadataMangerImpl#getExpiredOpenKeys

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

[jira] [Updated] (HDDS-4121) Implement OmMetadataMangerImpl#getExpiredOpenKeys

[ https://issues.apache.org/jira/browse/HDDS-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4121: - Affects Version/s: (was: 0.6.0) 1.0.0 > Implement

[jira] [Updated] (HDDS-4121) Implement OmMetadataMangerImpl#getExpiredOpenKeys

[ https://issues.apache.org/jira/browse/HDDS-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4121: - Priority: Major (was: Minor) > Implement OmMetadataMangerImpl#getExpiredOpenKeys >

[jira] [Updated] (HDDS-4121) Implement OmMetadataMangerImpl#getExpiredOpenKeys

[ https://issues.apache.org/jira/browse/HDDS-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4121: - Affects Version/s: 0.6.0 > Implement OmMetadataMangerImpl#getExpiredOpenKeys >

[jira] [Commented] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187869#comment-17187869 ] Bharat Viswanadham commented on HDDS-4097: -- Today this topic has been discussed in the community

[jira] [Resolved] (HDDS-4151) Skip the inputstream while offset larger than zero in s3g

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

[jira] [Updated] (HDDS-4146) Show the ScmId and ClusterId in the scm web ui.

[ https://issues.apache.org/jira/browse/HDDS-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4146: - Fix Version/s: (was: 1.1) 1.1.0 > Show the ScmId and ClusterId in

[jira] [Resolved] (HDDS-4145) Bump version to 1.1.0-SNAPSHOT on master

[ https://issues.apache.org/jira/browse/HDDS-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4145. -- Fix Version/s: 1.1.0 Resolution: Fixed > Bump version to 1.1.0-SNAPSHOT on

[jira] [Updated] (HDDS-4145) Bump version to 1.1.0-SNAPSHOT on master

[ https://issues.apache.org/jira/browse/HDDS-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4145: - Target Version/s: 1.1.0 (was: 0.7.0) > Bump version to 1.1.0-SNAPSHOT on master >

[jira] [Updated] (HDDS-4163) Enable filesystem semantics on bucket during creation of bucket

[ https://issues.apache.org/jira/browse/HDDS-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4163: - Summary: Enable filesystem semantics on bucket during creation of bucket (was: Enable

[jira] [Updated] (HDDS-4163) Enable filesystem semantics on bucket during creation

[ https://issues.apache.org/jira/browse/HDDS-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4163: - Description: HDDS-3955 added a config to ozoneManager ozone.om.enable.filesystem.paths to

[jira] [Created] (HDDS-4163) Enable filesystem semantics on bucket during creation

Bharat Viswanadham created HDDS-4163: Summary: Enable filesystem semantics on bucket during creation Key: HDDS-4163 URL: https://issues.apache.org/jira/browse/HDDS-4163 Project: Hadoop Distributed

[jira] [Updated] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4155: - Status: Patch Available (was: Open) > Directory and filename can end up with same name

  1   2   3   4   5   6   7   8   >