hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saad Mufti <saad.mu...@gmail.com>
Subject Re: Anyone Have A Workaround For HBASE-19681?
Date Mon, 26 Mar 2018 13:08:04 GMT
Restarting the region server worked for us to recover from this error.

----
Saad


On Fri, Mar 23, 2018 at 7:19 PM, Saad Mufti <saad.mufti@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
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message