Since I'm on my phone and am likely to be more terse, the extent referenced by the hole likely referenced files on HDFS that are recoverable. If you can locate those you can rebuild that hole, which I and others have done on this list. I will try and respond when I'm at the computer with more info if needed if someone else does not fill in my holey phone responses.
On Mon, Feb 27, 2017 at 8:47 PM, Marc P. <marc.par...@gmail.com> wrote: > Matt, > You can add replace/insert the key extents in which the hole exists. The > check simply looks at the prev end row key ( ~pr ) and ensure it matches > the actual last end row. You can insert the keys for that extent. I would > back up the table just in case. I thought there was a utility to fill in > this gap, but I'm on my phone, so I will look later. I wouldn't normally > advise the nuclear step of filling in the hole, but since ingest is backing > up I would triage to determine the cause at a later time if you are > struggling to maintain homeostasis in your ingest pipeline. > >
