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 >> Scanner timeout -- any reason not to raise?


Copy link to this message
-
Scanner timeout -- any reason not to raise?
We occasionally get scanner timeout errors such as "66698ms passed since the last invocation, timeout is currently set to 60000" when iterating a scanner through the Thrift API. Is there any reason not to raise the timeout to something larger than the default 60s? Put another way, what resources (and how much of them) does a scanner take up on a thrift server or region server?

Also, to confirm -- I believe "hbase.rpc.timeout" is the setting in question here, but someone please correct me if I'm wrong.

Thanks,
- Dan
+
Ted Yu 2013-03-17, 20:46
+
Dan Crosta 2013-03-17, 20:56
+
Ted Yu 2013-03-17, 21:20
+
Dan Crosta 2013-03-20, 16:32
+
Ted Yu 2013-03-20, 17:00
+
Bryan Beaudreault 2013-03-20, 17:05
+
Ted Yu 2013-03-20, 17:11
+
Bryan Beaudreault 2013-03-20, 17:39
+
Ted Yu 2013-03-20, 17:56
+
Bryan Beaudreault 2013-03-20, 19:13
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