On behalf of the Apache HBase PMC, I am pleased to announce that Tianhang
Tang(thangTang)
has accepted the PMC's invitation to become a committer on the project. We
appreciate all
of Tianhang's generous contributions thus far and look forward to his
continued involvement.
Congratulations and
Then Hadoop should add one and although we would need a reflection based check
in the interim we can converge toward the ideal.
In any case I believe we can avoid a direct dependency on Ozone and should
strongly avoid taking such unnecessary dependencies. The Hadoop and HBase build
dependency
Inline
> On Mar 15, 2023, at 2:11 PM, Wei-Chiu Chuang wrote:
>
> hsync/hflush, or any input/output stream APIs for that matter, can be
> probed using StreamCapabilities.hasCapabilitiy() API.
>
> lease recovery isn't (DistributedFIleSystem.recoverLease()). safe mode
> check isn't. There are a
hsync/hflush, or any input/output stream APIs for that matter, can be
probed using StreamCapabilities.hasCapabilitiy() API.
lease recovery isn't (DistributedFIleSystem.recoverLease()). safe mode
check isn't. There are a number of HDFS specific APIs that HBase uses.
I'm all for abstracting out FS
the check that Stephen is referring to is for logic around lease recovery
and not stream flush/sync. the lease recovery is specific to DFS IIRC and
doesn't have a FileSystem marker.
On Wed, Mar 15, 2023 at 3:22 PM Andrew Purtell wrote:
> So we can test StreamCapabilities in code, in worst case
So we can test StreamCapabilities in code, in worst case by wrapping some
probe code during startup with try-catch and examining the exception.
On Wed, Mar 15, 2023 at 1:09 PM Viraj Jasani wrote:
> As of today, both WAL impl (fshlog and asyncfs) throw
> StreamLacksCapabilityException if the FS
As of today, both WAL impl (fshlog and asyncfs) throw
StreamLacksCapabilityException if the FS Data OutputStream probe fails for
Hflush/Hsync:
StreamLacksCapabilityException(StreamCapabilities.HFLUSH)
and
StreamLacksCapabilityException(StreamCapabilities.HSYNC)
On Wed, Mar 15, 2023 at 12:51 PM
Does Hadoop have a marker interface that lets an application know its
FileSystem instances can support hsync/hflush? Ideally all we should need
to do is test with instanceof for that marker and use reflection (in the
worst case) to get a handle to the hsync or hflush method, and then call
it. This
Hi team,
Recently, Wei-Chiu and I have been discussing about if HBase can use
Ozone as another storage as WAL (see the hsync and hflush JIRAs [1])
and HFile, for HFile it’s pluggable by configuring the file system to
use Ozone File System (Ozone)
But we found that the WAL it’s a bit different,
chiranjeevi created HBASE-27721:
---
Summary: LEAK: RefCnt.release() was not called before it's
garbage-collected in regionserver
Key: HBASE-27721
URL: https://issues.apache.org/jira/browse/HBASE-27721
Nick Dimiduk created HBASE-27720:
Summary: TestClusterRestartFailover is flakey
Key: HBASE-27720
URL: https://issues.apache.org/jira/browse/HBASE-27720
Project: HBase
Issue Type: Task
[
https://issues.apache.org/jira/browse/HBASE-27715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-27715.
---
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to master and branch-2.
Thanks [~heliangjun]
Nick Dimiduk created HBASE-27719:
Summary: Fix surefire corrupted channel
Key: HBASE-27719
URL: https://issues.apache.org/jira/browse/HBASE-27719
Project: HBase
Issue Type: Task
13 matches
Mail list logo
