You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Saad Mufti <sa...@gmail.com> on 2018/03/23 23:19:32 UTC
Anyone Have A Workaround For HBASE-19681?
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 earlier in a compaction thread on the same missing file.
Is there anyway we can recover this db? We ran hbck -details and it
reported no errors.
Thanks.
----
Saad
Re: Anyone Have A Workaround For HBASE-19681?
Posted by Saad Mufti <sa...@gmail.com>.
Restarting the region server worked for us to recover from this error.
----
Saad
On Fri, Mar 23, 2018 at 7:19 PM, Saad Mufti <sa...@gmail.com> wrote:
> 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 earlier in a compaction thread on the same missing file.
>
> Is there anyway we can recover this db? We ran hbck -details and it
> reported no errors.
>
> Thanks.
>
> ----
> Saad
>
>