Thanks.
Saad
On Wed, Mar 21, 2018 at 3:04 PM, Ted Yu wrote:
> Looking at
> hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java in
> branch-1.4 :
>
> boolean[] setSplitOrMergeEnabled(final boolean enabled, final boolean
> synchronous,
>
Thanks.
Saad
On Wed, Mar 21, 2018 at 2:33 PM, Vladimir Rodionov
wrote:
> >>So my question is whether taking a snapshot is supposed to work even with
> >>regions being moved around. In our case it is usually only a couple here
> >>and there.
>
> No, if region was moved, split or merged duri
We are facing the exact same symptoms in HBase 1.4.0 running on AWS EMR
based cluster, and desperately need to take a snapshot to feed a downstream
job. So far we have tried using the "assign" command on all regions
involved to move them around but the snapshot still fails. Also saw the
same error
Hi all,
I cannot find any good information about ASYNC_WAL semantics.
As much as I understand the worst I can get - data loss in case of region
failure.
But the question I have - can it affect visibility in any way? Does it
still follow the principle "When a client receives a "success" response for
Hi all,
I cannot find any good information about ASYNC_WAL semantics.
As much as I understand the worst I can get - data loss in case of region
failure.
But the question I have - can it affect visibility in any way? Does it
still follow the principle "When a client receives a "success" response for
