> Is this the same as the hregion.max.filesize setting?

Yes.

>
> If HConnectionManager is doing it is it then hbase memory of Thrift server
> memory that caches the region locations?

That's the same JVM, so same memory? I'm not sure what you're asking
about but if it can help, you give more memory to the thrift server
you need to edit this hbase-env.sh line:

# export HBASE_THRIFT_OPTS="$HBASE_THRIFT_OPTS $HBASE_JMX_BASE
-Dcom.sun.management.jmxremote.port=10103"

> I will try this. We have sparse data but maybe setting very high will take
> the hit up front. Is this setting only used when a region location is not in
> cache? If we set this very high we do not want to take the hit on every
> read.

I'd say try it on fake data that was pre-splitting thousands of times.
You'll take the hit only when the region is not in cache (actually the
code seems wrong about it... let me check something and get back to
you).

J-D

Reply via email to