[jira] [Commented] (HADOOP-15621) S3Guard: Implement time-based (TTL) expiry for Authoritative Directory Listing

2018-09-27 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631196#comment-16631196 ] Gabor Bota commented on HADOOP-15621: - Finally, I've uploaded the second patch for

[jira] [Commented] (HADOOP-15798) ITestS3GuardListConsistency#testConsistentListAfterDelete failing with LocalMetadataStore

2018-09-30 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633631#comment-16633631 ] Gabor Bota commented on HADOOP-15798: - Thanks [~ste...@apache.org]! I'll add that w

[jira] [Assigned] (HADOOP-15798) ITestS3GuardListConsistency#testConsistentListAfterDelete failing with LocalMetadataStore

2018-09-30 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-15798: --- Assignee: Gabor Bota > ITestS3GuardListConsistency#testConsistentListAfterDelete failing w

[jira] [Commented] (HADOOP-15799) ITestS3AEmptyDirectory#testDirectoryBecomesEmpty fails when running with dynamo

2018-09-30 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633632#comment-16633632 ] Gabor Bota commented on HADOOP-15799: - us-west-1, and I was in that region when the

[jira] [Updated] (HADOOP-15800) ITestS3GuardListConsistency#testConsistentListAfterDelete fails when running with dynamo

2018-09-30 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15800: Description: I've seen a new failure when running verify for HADOOP-15621. First I thought it wa

[jira] [Assigned] (HADOOP-15799) ITestS3AEmptyDirectory#testDirectoryBecomesEmpty fails when running with dynamo

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-15799: --- Assignee: Gabor Bota > ITestS3AEmptyDirectory#testDirectoryBecomesEmpty fails when running

[jira] [Commented] (HADOOP-15799) ITestS3AEmptyDirectory#testDirectoryBecomesEmpty fails when running with dynamo

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633720#comment-16633720 ] Gabor Bota commented on HADOOP-15799: - Ok, so I think I've figured out the issue -

[jira] [Comment Edited] (HADOOP-15799) ITestS3AEmptyDirectory#testDirectoryBecomesEmpty fails when running with dynamo

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633720#comment-16633720 ] Gabor Bota edited comment on HADOOP-15799 at 10/1/18 8:38 AM: ---

[jira] [Issue Comment Deleted] (HADOOP-15799) ITestS3AEmptyDirectory#testDirectoryBecomesEmpty fails when running with dynamo

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15799: Comment: was deleted (was: Ok, so I think I've figured out the issue - I had the failure with the

[jira] [Commented] (HADOOP-15799) ITestS3AEmptyDirectory#testDirectoryBecomesEmpty fails when running with dynamo

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633724#comment-16633724 ] Gabor Bota commented on HADOOP-15799: - Cleaned up my test setup, and tested this ag

[jira] [Commented] (HADOOP-15621) S3Guard: Implement time-based (TTL) expiry for Authoritative Directory Listing

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633804#comment-16633804 ] Gabor Bota commented on HADOOP-15621: - re-tested {{mvn -Dparallel-tests -DtestsThre

[jira] [Updated] (HADOOP-15621) S3Guard: Implement time-based (TTL) expiry for Authoritative Directory Listing

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15621: Status: Patch Available (was: In Progress) > S3Guard: Implement time-based (TTL) expiry for Auth

[jira] [Commented] (HADOOP-15796) ClassCastException: S3AFileSystem cannot be cast to MockS3AFileSystem when fs caching is disabled

2018-10-01 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634181#comment-16634181 ] Gabor Bota commented on HADOOP-15796: - Thanks for looking in this [~ste...@apache.o

[jira] [Commented] (HADOOP-15796) ClassCastException: S3AFileSystem cannot be cast to MockS3AFileSystem when fs caching is disabled

2018-10-02 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635524#comment-16635524 ] Gabor Bota commented on HADOOP-15796: - The following error keeps popping up when ru

[jira] [Comment Edited] (HADOOP-15796) ClassCastException: S3AFileSystem cannot be cast to MockS3AFileSystem when fs caching is disabled

2018-10-02 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635524#comment-16635524 ] Gabor Bota edited comment on HADOOP-15796 at 10/2/18 1:56 PM: ---

[jira] [Assigned] (HADOOP-15796) ClassCastException: S3AFileSystem cannot be cast to MockS3AFileSystem when fs caching is disabled

2018-10-02 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-15796: --- Assignee: Gabor Bota > ClassCastException: S3AFileSystem cannot be cast to MockS3AFileSyst

[jira] [Created] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

2018-10-04 Thread Gabor Bota (JIRA)
Gabor Bota created HADOOP-15819: --- Summary: S3A integration test failures: FileSystem is closed! - without parallel test run Key: HADOOP-15819 URL: https://issues.apache.org/jira/browse/HADOOP-15819 Proj

[jira] [Updated] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

2018-10-04 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15819: Attachment: S3ACloseEnforcedFileSystem.java > S3A integration test failures: FileSystem is closed

[jira] [Updated] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

2018-10-04 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15819: Attachment: closed_fs_closers_example_5klines.log.zip > S3A integration test failures: FileSystem

[jira] [Commented] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

2018-10-04 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638306#comment-16638306 ] Gabor Bota commented on HADOOP-15819: - >From that perspective, every test could use

[jira] [Commented] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

2018-10-04 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638351#comment-16638351 ] Gabor Bota commented on HADOOP-15819: - So that's {{fs.s3a.impl.disable.cache}} (S3

[jira] [Commented] (HADOOP-16550) Spark config name error on the Launching Applications Using Docker Containers page

2019-09-05 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923501#comment-16923501 ] Gabor Bota commented on HADOOP-16550: - Sure, thanks for the contribution [~attilapi

[jira] [Updated] (HADOOP-16550) Spark config name error on the Launching Applications Using Docker Containers page

2019-09-05 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16550: Description: On the "Launching Applications Using Docker Containers" page at the "Example: Spark

[jira] [Commented] (HADOOP-16550) Spark config name error on the Launching Applications Using Docker Containers page

2019-09-06 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924058#comment-16924058 ] Gabor Bota commented on HADOOP-16550: - Merged PR #9 > Spark config name error on t

[jira] [Resolved] (HADOOP-16550) Spark config name error on the Launching Applications Using Docker Containers page

2019-09-06 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16550. - Resolution: Fixed > Spark config name error on the Launching Applications Using Docker Containe

[jira] [Commented] (HADOOP-16507) S3Guard fsck: Add option to configure severity (level) for the scan

2019-09-10 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926405#comment-16926405 ] Gabor Bota commented on HADOOP-16507: - ++ additional task: Add `-verbose` arg to t

[jira] [Created] (HADOOP-16563) S3Guard fsck: Detect if a directory if authoritative and highlight errors if detected in it

2019-09-12 Thread Gabor Bota (Jira)
Gabor Bota created HADOOP-16563: --- Summary: S3Guard fsck: Detect if a directory if authoritative and highlight errors if detected in it Key: HADOOP-16563 URL: https://issues.apache.org/jira/browse/HADOOP-16563

[jira] [Created] (HADOOP-16564) S3Guarld fsck: Add docs to the first iteration (S3->ddbMS, -verify)

2019-09-12 Thread Gabor Bota (Jira)
Gabor Bota created HADOOP-16564: --- Summary: S3Guarld fsck: Add docs to the first iteration (S3->ddbMS, -verify) Key: HADOOP-16564 URL: https://issues.apache.org/jira/browse/HADOOP-16564 Project: Hadoop C

[jira] [Commented] (HADOOP-16423) S3Guarld fsck: Check metadata consistency from S3 to metadatastore (log)

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928449#comment-16928449 ] Gabor Bota commented on HADOOP-16423: - +1 from [~ste...@apache.org] on PR #1208. Co

[jira] [Created] (HADOOP-16565) Fix "com.amazonaws.SdkClientException: Unable to find a region via the region provider chain."

2019-09-12 Thread Gabor Bota (Jira)
Gabor Bota created HADOOP-16565: --- Summary: Fix "com.amazonaws.SdkClientException: Unable to find a region via the region provider chain." Key: HADOOP-16565 URL: https://issues.apache.org/jira/browse/HADOOP-16565

[jira] [Updated] (HADOOP-16566) S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16566: Affects Version/s: 3.3.0 > S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of > com.g

[jira] [Created] (HADOOP-16566) S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch

2019-09-12 Thread Gabor Bota (Jira)
Gabor Bota created HADOOP-16566: --- Summary: S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch Key: HADOOP-16566 URL: https://issues.apache.org/jira/browse/HADOOP-16566

[jira] [Updated] (HADOOP-16566) S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16566: Component/s: fs/s3 > S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of > com.google.

[jira] [Work started] (HADOOP-16566) S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16566 started by Gabor Bota. --- > S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of > com.google.co

[jira] [Commented] (HADOOP-16566) S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928693#comment-16928693 ] Gabor Bota commented on HADOOP-16566: - maybe, but it would be better to update guav

[jira] [Resolved] (HADOOP-16423) S3Guarld fsck: Check metadata consistency from S3 to metadatastore (log)

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16423. - Resolution: Fixed > S3Guarld fsck: Check metadata consistency from S3 to metadatastore (log) >

[jira] [Commented] (HADOOP-16566) S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928734#comment-16928734 ] Gabor Bota commented on HADOOP-16566: - +1 by [~ste...@apache.org] on #1433 PR. Com

[jira] [Resolved] (HADOOP-16566) S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of com.google.common.base.Stopwatch

2019-09-12 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16566. - Resolution: Fixed > S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of > com.google

[jira] [Commented] (HADOOP-16565) Fix "com.amazonaws.SdkClientException: Unable to find a region via the region provider chain."

2019-09-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929242#comment-16929242 ] Gabor Bota commented on HADOOP-16565: - I don't have any STS endpoint besides {nofor

[jira] [Commented] (HADOOP-16565) Fix "com.amazonaws.SdkClientException: Unable to find a region via the region provider chain."

2019-09-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929284#comment-16929284 ] Gabor Bota commented on HADOOP-16565: - It worked with the following STS config: {n

[jira] [Resolved] (HADOOP-16565) Fix "com.amazonaws.SdkClientException: Unable to find a region via the region provider chain."

2019-09-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16565. - Resolution: Workaround > Fix "com.amazonaws.SdkClientException: Unable to find a region via the

[jira] [Work started] (HADOOP-16520) race condition in DDB table init and waiting threads

2019-09-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16520 started by Gabor Bota. --- > race condition in DDB table init and waiting threads > ---

[jira] [Assigned] (HADOOP-16520) race condition in DDB table init and waiting threads

2019-09-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-16520: --- Assignee: Gabor Bota > race condition in DDB table init and waiting threads >

[jira] [Reopened] (HADOOP-16565) Fix "com.amazonaws.SdkClientException: Unable to find a region via the region provider chain."

2019-09-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reopened HADOOP-16565: - Reopened to add a message. > Fix "com.amazonaws.SdkClientException: Unable to find a region via th

[jira] [Updated] (HADOOP-16565) Region must be provided when requesting session credentials or SdkClientException will be thrown

2019-09-16 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16565: Summary: Region must be provided when requesting session credentials or SdkClientException will b

[jira] [Work started] (HADOOP-16565) Region must be provided when requesting session credentials or SdkClientException will be thrown

2019-09-16 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16565 started by Gabor Bota. --- > Region must be provided when requesting session credentials or > SdkClientExc

[jira] [Updated] (HADOOP-16565) Region must be provided when requesting session credentials or SdkClientException will be thrown

2019-09-16 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16565: Status: Patch Available (was: In Progress) > Region must be provided when requesting session cre

[jira] [Commented] (HADOOP-16565) Region must be provided when requesting session credentials or SdkClientException will be thrown

2019-09-18 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932216#comment-16932216 ] Gabor Bota commented on HADOOP-16565: - +1 from [~ste...@apache.org] on PR 1454. Com

[jira] [Work stopped] (HADOOP-16520) race condition in DDB table init and waiting threads

2019-09-18 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16520 stopped by Gabor Bota. --- > race condition in DDB table init and waiting threads > ---

[jira] [Assigned] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-09-18 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-16484: --- Assignee: Gabor Bota > S3A to warn or fail if S3Guard is disabled > --

[jira] [Commented] (HADOOP-16547) s3guard prune command doesn't get AWS auth chain from FS

2019-09-18 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932692#comment-16932692 ] Gabor Bota commented on HADOOP-16547: - +1 on PR 1402. Committed. > s3guard prune c

[jira] [Resolved] (HADOOP-16547) s3guard prune command doesn't get AWS auth chain from FS

2019-09-18 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16547. - Resolution: Fixed > s3guard prune command doesn't get AWS auth chain from FS >

[jira] [Updated] (HADOOP-16565) Region must be provided when requesting session credentials or SdkClientException will be thrown

2019-09-23 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16565: Resolution: Fixed Status: Resolved (was: Patch Available) > Region must be provided when

[jira] [Commented] (HADOOP-16138) hadoop fs mkdir / of nonexistent abfs container raises NPE

2019-09-23 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935762#comment-16935762 ] Gabor Bota commented on HADOOP-16138: - +1 by [~ste...@apache.org] on PR #1302. Comm

[jira] [Resolved] (HADOOP-16138) hadoop fs mkdir / of nonexistent abfs container raises NPE

2019-09-23 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16138. - Target Version/s: 3.3.0 Resolution: Fixed > hadoop fs mkdir / of nonexistent abfs con

[jira] [Commented] (HADOOP-16138) hadoop fs mkdir / of nonexistent abfs container raises NPE

2019-09-25 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937551#comment-16937551 ] Gabor Bota commented on HADOOP-16138: - That is true. Sorry [~ayushtkn]. The way I

[jira] [Resolved] (HADOOP-16529) Allow AZURE_CREATE_REMOTE_FILESYSTEM_DURING_INITIALIZATION to be set from abfs.xml property

2019-09-25 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16529. - Resolution: Workaround > Allow AZURE_CREATE_REMOTE_FILESYSTEM_DURING_INITIALIZATION to be set f

[jira] [Assigned] (HADOOP-16579) Upgrade to Apache Curator 4.2.0 in Hadoop

2019-09-25 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-16579: --- Assignee: Norbert Kalmar > Upgrade to Apache Curator 4.2.0 in Hadoop > ---

[jira] [Commented] (HADOOP-16520) race condition in DDB table init and waiting threads

2019-09-26 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938690#comment-16938690 ] Gabor Bota commented on HADOOP-16520: - I'll try to solve this the other way: add th

[jira] [Work started] (HADOOP-16520) race condition in DDB table init and waiting threads

2019-09-28 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16520 started by Gabor Bota. --- > race condition in DDB table init and waiting threads > ---

[jira] [Assigned] (HADOOP-16349) DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry

2019-10-01 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-16349: --- Assignee: Gabor Bota > DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on

[jira] [Work started] (HADOOP-16349) DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry

2019-10-01 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16349 started by Gabor Bota. --- > DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry > --

[jira] [Commented] (HADOOP-16349) DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry

2019-10-01 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942161#comment-16942161 ] Gabor Bota commented on HADOOP-16349: - I'm going to fix this with HADOOP-16520 >

[jira] [Updated] (HADOOP-16520) Race condition in DDB table init and waiting threads

2019-10-11 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16520: Summary: Race condition in DDB table init and waiting threads (was: race condition in DDB table

[jira] [Commented] (HADOOP-16520) Race condition in DDB table init and waiting threads

2019-10-11 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949339#comment-16949339 ] Gabor Bota commented on HADOOP-16520: - +1 on #1576 from [~ste...@apache.org]. Commi

[jira] [Resolved] (HADOOP-16520) Race condition in DDB table init and waiting threads

2019-10-11 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16520. - Resolution: Fixed > Race condition in DDB table init and waiting threads >

[jira] [Commented] (HADOOP-16349) DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry

2019-10-11 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949341#comment-16949341 ] Gabor Bota commented on HADOOP-16349: - https://github.com/apache/hadoop/pull/1576 F

[jira] [Resolved] (HADOOP-16349) DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry

2019-10-11 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16349. - Resolution: Fixed > DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry >

[jira] [Commented] (HADOOP-16653) S3Guard DDB overreacts to no tag access

2019-10-14 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951043#comment-16951043 ] Gabor Bota commented on HADOOP-16653: - It was cleary in the docs, so I'll update th

[jira] [Comment Edited] (HADOOP-16653) S3Guard DDB overreacts to no tag access

2019-10-14 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951043#comment-16951043 ] Gabor Bota edited comment on HADOOP-16653 at 10/14/19 2:47 PM: --

[jira] [Commented] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-10-16 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952938#comment-16952938 ] Gabor Bota commented on HADOOP-16484: - I removed status (merged with inform) so at

[jira] [Comment Edited] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-10-16 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952938#comment-16952938 ] Gabor Bota edited comment on HADOOP-16484 at 10/16/19 3:29 PM: --

[jira] [Comment Edited] (HADOOP-16424) S3Guard fsck: Check internal consistency of the MetadataStore

2019-10-17 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898870#comment-16898870 ] Gabor Bota edited comment on HADOOP-16424 at 10/17/19 11:35 AM: -

[jira] [Commented] (HADOOP-16424) S3Guard fsck: Check internal consistency of the MetadataStore

2019-10-17 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953649#comment-16953649 ] Gabor Bota commented on HADOOP-16424: - Our code should not be creating orphan entri

[jira] [Commented] (HADOOP-16653) S3Guard DDB overreacts to no tag access

2019-10-28 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960909#comment-16960909 ] Gabor Bota commented on HADOOP-16653: - +1 on PR#1660 from [~ste...@apache.org]. Com

[jira] [Resolved] (HADOOP-16653) S3Guard DDB overreacts to no tag access

2019-10-28 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16653. - Resolution: Fixed > S3Guard DDB overreacts to no tag access > -

[jira] [Work started] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-10-28 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16484 started by Gabor Bota. --- > S3A to warn or fail if S3Guard is disabled > -

[jira] [Work started] (HADOOP-16424) S3Guard fsck: Check internal consistency of the MetadataStore

2019-10-28 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16424 started by Gabor Bota. --- > S3Guard fsck: Check internal consistency of the MetadataStore > --

[jira] [Commented] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-04 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966594#comment-16966594 ] Gabor Bota commented on HADOOP-16484: - +1 from [~ste...@apache.org] on PR #1661, co

[jira] [Resolved] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-04 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota resolved HADOOP-16484. - Fix Version/s: 3.3.0 Target Version/s: 3.3.0 (was: 3.2.2) Resolution: Fixed >

[jira] [Assigned] (HADOOP-16473) S3Guard prune to only remove auth dir marker if files (not tombstones) are removed

2019-11-07 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-16473: --- Assignee: Gabor Bota > S3Guard prune to only remove auth dir marker if files (not tombston

[jira] [Commented] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-08 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970505#comment-16970505 ] Gabor Bota commented on HADOOP-16484: - Sure, I'm happy to do this. > S3A to warn

[jira] [Work started] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-16484 started by Gabor Bota. --- > S3A to warn or fail if S3Guard is disabled > -

[jira] [Updated] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-13 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16484: Status: Patch Available (was: In Progress) https://github.com/apache/hadoop/pull/1714 as the add

[jira] [Commented] (HADOOP-16709) Consider having the ability to turn off TTL in S3Guard + Authoritative mode

2019-11-14 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974210#comment-16974210 ] Gabor Bota commented on HADOOP-16709: - Sure. I can do this. The general idea behind

[jira] [Assigned] (HADOOP-16706) ITestClientUrlScheme fails for accounts which don't support HTTP

2019-11-14 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-16706: --- Assignee: Gabor Bota > ITestClientUrlScheme fails for accounts which don't support HTTP >

[jira] [Commented] (HADOOP-16709) Consider having the ability to turn off TTL in S3Guard + Authoritative mode

2019-11-15 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975000#comment-16975000 ] Gabor Bota commented on HADOOP-16709: - Talking offline with [~ste...@apache.org] we

[jira] [Assigned] (HADOOP-16709) Consider having the ability to turn off TTL in S3Guard + Authoritative mode

2019-11-15 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota reassigned HADOOP-16709: --- Assignee: Gabor Bota > Consider having the ability to turn off TTL in S3Guard + Authoritat

[jira] [Updated] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-18 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-16484: Resolution: Fixed Status: Resolved (was: Patch Available) > S3A to warn or fail if S3Gua

[jira] [Commented] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-18 Thread Gabor Bota (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976514#comment-16976514 ] Gabor Bota commented on HADOOP-16484: - Got +1 on GitHub Pull Request #1714 from [~s

[jira] [Commented] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642218#comment-16642218 ] Gabor Bota commented on HADOOP-15827: - I'll check it soon. > NPE in DynamoDBMetada

[jira] [Commented] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642265#comment-16642265 ] Gabor Bota commented on HADOOP-15827: - I'm not able to reproduce the issue by runni

[jira] [Commented] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642283#comment-16642283 ] Gabor Bota commented on HADOOP-15827: - I'm not really sure if this is happening in

[jira] [Commented] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642286#comment-16642286 ] Gabor Bota commented on HADOOP-15827: - But line 644 is just a comment. How can it b

[jira] [Comment Edited] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642283#comment-16642283 ] Gabor Bota edited comment on HADOOP-15827 at 10/8/18 6:36 PM: ---

[jira] [Issue Comment Deleted] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15827: Comment: was deleted (was: But line 644 is just a comment. How can it be?) > NPE in DynamoDBMeta

[jira] [Comment Edited] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642283#comment-16642283 ] Gabor Bota edited comment on HADOOP-15827 at 10/8/18 7:11 PM: ---

[jira] [Commented] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642397#comment-16642397 ] Gabor Bota commented on HADOOP-15827: - Thanks, it makes sense now. I was able to re

[jira] [Updated] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15827: Attachment: HADOOP-15827.001.patch > NPE in DynamoDBMetadataStore.lambda$listChildren for root +

[jira] [Updated] (HADOOP-15827) NPE in DynamoDBMetadataStore.lambda$listChildren for root + auth s3guard

2018-10-08 Thread Gabor Bota (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Bota updated HADOOP-15827: Status: Patch Available (was: Open) > NPE in DynamoDBMetadataStore.lambda$listChildren for root

<    5   6   7   8   9   10   11   12   13   >