On Thu, Jan 12, 2012 at 1:30 PM, James Estes wrote:
> Thanks for the advice. We don't have those logs anymore. Is there
> anyway for hbase to recover gracefully here? The compactions piled up
> behind it until we bounced the region server. Is there already a
> ticket filed for recovering from
Thanks for the advice. We don't have those logs anymore. Is there
anyway for hbase to recover gracefully here? The compactions piled up
behind it until we bounced the region server. Is there already a
ticket filed for recovering from double assignment issues like this?
Our current plan would be
On Mon, Jan 9, 2012 at 1:57 PM, James Estes wrote:
> Should we file a ticket for this issue? FWIW we got this fixed (not
> sure if we actually lost any data though). We had to bounce the region
> server (non-gracefully). The region server seemed to have some stale
> file handles into hdfs...open
On Thu, Dec 22, 2011 at 1:34 PM, James Estes wrote:
> We have a 6 node 0.90.3-cdh3u1 cluster. We have 8092 regions. I
> realize we have too many regions and too few nodes…we're addressing
> that.
Good.
> We currently have an issue where we seem to have lost region
> data. When data is request
Should we file a ticket for this issue? FWIW we got this fixed (not
sure if we actually lost any data though). We had to bounce the region
server (non-gracefully). The region server seemed to have some stale
file handles into hdfs...open inputstreams to files that were long
deleted in hdfs. Any c
We have a 6 node 0.90.3-cdh3u1 cluster. We have 8092 regions. I
realize we have too many regions and too few nodes…we're addressing
that. We currently have an issue where we seem to have lost region
data. When data is requested for a couple of our regions, we get
errors like the following on th
