[
https://issues.apache.org/jira/browse/HBASE-18784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239565#comment-16239565
]
Sean Busbey commented on HBASE-18784:
-------------------------------------
{code}
Busbey-MBA:hbase busbey$ ./dev-support/findHangingTests.py
https://builds.apache.org/job/PreCommit-HBASE-Build/9632/artifact/patchprocess/patch-unit-hbase-server.txt
Fetching
https://builds.apache.org/job/PreCommit-HBASE-Build/9632/artifact/patchprocess/patch-unit-hbase-server.txt
Printing hanging tests
Hanging test : org.apache.hadoop.hbase.regionserver.wal.TestLogRollingNoCluster
Printing Failing tests
Busbey-MBA:hbase busbey$
{code}
checking on it now.
> Use of filesystem that requires hflush / hsync / append / etc should query
> outputstream capabilities
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-18784
> URL: https://issues.apache.org/jira/browse/HBASE-18784
> Project: HBase
> Issue Type: Improvement
> Components: Filesystem Integration
> Affects Versions: 1.4.0, 2.0.0-alpha-2
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Fix For: 2.1.0, 1.5.0
>
> Attachments: HBASE-18784-branch-1.v2.patch, HBASE-18784.0.patch,
> HBASE-18784.1.patch, HBASE-18784.2.patch
>
>
> In places where we rely on the underlying filesystem holding up the promises
> of hflush/hsync (most importantly the WAL), we should use the new interfaces
> provided by HDFS-11644 to fail loudly when they are not present (e.g. on S3,
> on EC mounts, etc).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
