[
https://issues.apache.org/jira/browse/IMPALA-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731960#comment-16731960
]
ASF subversion and git services commented on IMPALA-6544:
---------------------------------------------------------
Commit 6f6d1f64a10f9a958dfa6162ec8bdab4cdcc6d92 in impala's branch
refs/heads/master from Philip Zeyliger
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=6f6d1f6 ]
IMPALA-6544: S3 tests fail because S3 is eventually consistent.
This skips test_insert_parquet on S3, as S3's eventually consistent
behavior is exposing us to "file not found" errors.
To remove this band-aid, we'll need to either handle s3 consistency
natively in some way, or to retry certain tests.
Note that this may be only a drop in a big bucket at the moment;
I think we see these issues in a variety of places.
Change-Id: I22e7620e97366bece69a20885f5c3b75de05fab6
Reviewed-on: http://gerrit.cloudera.org:8080/12127
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Lack of S3 consistency leads to rare test failures
> --------------------------------------------------
>
> Key: IMPALA-6544
> URL: https://issues.apache.org/jira/browse/IMPALA-6544
> Project: IMPALA
> Issue Type: Task
> Components: Frontend
> Affects Versions: Impala 2.8.0
> Reporter: Sailesh Mukil
> Priority: Major
> Labels: S3, broken-build, consistency, flaky, test-framework
>
> Every now and then, we hit a flaky test on S3 runs due to files missing when
> they should be present, and vice versa. We could consider running our tests
> (or a subset of our tests) with S3Guard to avoid these problems, however rare
> they are.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
