Additional information)
I am currently using hbase-1, but I am preparing to upgrade to hbase-2.
2020. 3. 17. 11:51, Kang Minwoo
mailto:minwoo.k...@outlook.com>> 작성:
Thank you for kindly reply.
I think the solution you gave me is really good.
I didn't know that before, so I took a different
Thank you for kindly reply.
I think the solution you gave me is really good.
I didn't know that before, so I took a different approach.
I made a new configuration to check that a system is stopped by time.
And I create a issue[1] and attach a patch[2].
I am not sure this is a proper approach.
Thanks for the detail below. Helped.
In your custom scanner, can you check RegionCoprocessorEnvironment on each
next invocation? RCE gives you access to the hosting RegionServer via
/** @return reference to the region server services */
RegionServerServices getRegionServerServices();
You can
HBase version is 1.2.9
The region was closed after a few minutes of about 1min.
I use a coprocessor that implements BaseRegionObserver.
The purpose is for deleting data with an expired retention period.
My coprocessor return Custom scanner in BaseRegionObserver.preCompact and when
scan type is
On Mon, Feb 24, 2020 at 8:20 PM Kang Minwoo wrote:
> Hello Users.
>
> Is there any way to check the system stop is requested in
> performCompaction over time?
>
> When the region got a close request, the region should wait there is no
> compaction and flush.
> However, in performCompaction
Hello Users.
Is there any way to check the system stop is requested in performCompaction
over time?
When the region got a close request, the region should wait there is no
compaction and flush.
However, in performCompaction method checked periodically only by write bytes.
If write bytes is too
