Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> errors after upgrade


Copy link to this message
-
Re: errors after upgrade
Nope, there are no timeouts, the queries are fast and 95% in cache,
this looks like a region server tried to read some memory buffer and
get 0 bytes in return.

-Jack

On Mon, Nov 14, 2011 at 3:10 PM, Stack <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 14, 2011 at 3:05 PM, Jack Levin <[EMAIL PROTECTED]> wrote:
>> No custom code. and I did enable RPC logging to see what might be
>> wrong, but nothing is showing that would be considered an error.  Its
>> happening on two of our clusters that run different functions, one
>> uses thrift, and the other is REST.  From the looks of the stack trace
>> it seems like a low level java error.   One of our clusters runs scans
>> without filters, and the other is just PUT and GET, both get errors.
>> We can add some more debug code into the source and try if you can
>> suggest of a way to produce more debugging info.
>>
>
> What about other side of the connection? Is client going away on us?
> Maybe these are slow queries and client has given up by the time the
> server gets around to processing the request?
>
> St.Ack
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB