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 Plain View
HBase >> mail # user >> Re: Coprocessor execution - HBaseServer: (responseTooSlow) java.nio.channels.ClosedChannelException


+
Stack 2011-09-23, 16:29
+
Mayuresh 2011-09-26, 08:56
+
Mayuresh 2011-09-26, 10:22
+
Mayuresh 2011-09-26, 14:41
+
Stack 2011-09-26, 16:25
Copy link to this message
-
Re: Coprocessor execution - HBaseServer: (responseTooSlow) java.nio.channels.ClosedChannelException
Hey Mayuresh!
Can you try setting the Scan cache value to a good number (like a  few
100 or more)?

Cheers,
Himanshu
On Mon, Sep 26, 2011 at 9:01 AM, Himanshu Vashishtha
<[EMAIL PROTECTED]> wrote:
>
> Hey Mayuresh!
> Can you try setting the Scan cache value to a good number (like a  few 100 or more)?
>
> Cheers,
> Himanshu
>
> On Mon, Sep 26, 2011 at 8:41 AM, Mayuresh <[EMAIL PROTECTED]> wrote:
>>
>> Guys any guidance? Am not getting any clue onto how to solve this problem.
>>
>> On Mon, Sep 26, 2011 at 3:52 PM, Mayuresh <[EMAIL PROTECTED]> wrote:
>> > I increased the leases in hbase-site.xml to around 50 minutes:
>> >
>> >  <property>
>> >    <name>hbase.regionserver.lease.period</name>
>> >    <!--value>60000</value-->
>> >    <value>3000000</value>
>> >    <description>HRegion server lease period in milliseconds. Default is
>> >    60 seconds. Clients must report in within this period else they are
>> >    considered dead.</description>
>> >  </property>
>> >
>> > However I still fail with the same error:
>> >
>> > 2011-09-26 15:50:28,857 WARN org.apache.hadoop.ipc.HBaseServer:
>> > (responseTooSlow):
>> > {"processingtimems":118696,"call":"execCoprocessor([B@5b0e6f59,
>> > getAvg(org.apache.hadoop.hbase.client.coprocessor.LongColumnInterpreter@10b06ac3,
>> > {\"timeRange\":[0,9223372036854775807],\"batch\":-1,\"startRow\":\"\",\"stopRow\":\"\",\"totalColumns\":0,\"cacheBlocks\":true,\"families\":{\"data\":[]},\"maxVersions\":1,\"caching\":-1}))","client":"137.72.240.180:54843","starttimems":1317032310155,"queuetimems":9,"class":"HRegionServer","responsesize":0,"method":"execCoprocessor"}
>> > 2011-09-26 15:50:28,872 WARN org.apache.hadoop.ipc.HBaseServer: IPC
>> > Server Responder, call execCoprocessor([B@5b0e6f59,
>> > getAvg(org.apache.hadoop.hbase.client.coprocessor.LongColumnInterpreter@10b06ac3,
>> > {"timeRange":[0,9223372036854775807],"batch":-1,"startRow":"","stopRow":"","totalColumns":0,"cacheBlocks":true,"families":{"data":[]},"maxVersions":1,"caching":-1}))
>> > from 137.72.240.180:54843: output error
>> > 2011-09-26 15:50:28,873 WARN org.apache.hadoop.ipc.HBaseServer: IPC
>> > Server handler 4 on 60020 caught:
>> > java.nio.channels.ClosedChannelException
>> >        at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:133)
>> >        at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324)
>> >        at org.apache.hadoop.hbase.ipc.HBaseServer.channelWrite(HBaseServer.java:1501)
>> >        at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.processResponse(HBaseServer.java:876)
>> >        at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.doRespond(HBaseServer.java:955)
>> >        at org.apache.hadoop.hbase.ipc.HBaseServer$Call.sendResponseIfReady(HBaseServer.java:390)
>> >        at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1240)
>> >
>> > What does this responseTooSlow and "output error" mean? Any clues to
>> > find whats causing this?
>> >
>> > Thanks.
>> >
>> >
>> > On Mon, Sep 26, 2011 at 2:26 PM, Mayuresh <[EMAIL PROTECTED]> wrote:
>> >> Hi Ted,
>> >>
>> >> Yes I am aware that this isn't a good setup. I am working on
>> >> understanding the coprocessors before I can use a bigger setup.
>> >>
>> >> I am talking about the prez at
>> >> https://hbase.s3.amazonaws.com/hbase/HBase-CP-HUG10.pdf by Andrew
>> >> Purtell, slide 5 :
>> >>
>> >> <quote>
>> >> For long running jobs the client must periodically poll status to keep it
>> >> alive; jobs without interest will be cancelled
>> >> </quote>
>> >>
>> >>
>> >> On Mon, Sep 26, 2011 at 2:08 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>> >>> Looks like my response to user@ got bounced.
>> >>>
>> >>> Himanshu is continuing the work on HBASE-3607
>> >>>
>> >>>>> Currently all the regions are on a single region server.
>> >>> I don't think the above is a good setup.
>> >>>
>> >>>>> It was mentioned to poll the job status periodically to avoid timeouts.
>> >>> Can you tell us more about the presentation ? Normally you can include the
+
Mayuresh 2011-09-26, 17:55
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