Interesting - this issue would certainly go away with local mode as
there's no thrift call to fail. I'd very much prefer to run HMS as a
centralized service though.
Thanks for the info - I'll have to take a look at how the thrift
client handles timeouts/reconnects/etc.
--travis
On Wed, Aug 1, 2
The two setup options are:
cli->thriftmetastore->jdbc
cli->jdbc (used to be called local mode)
localmode has less moving parts so I prefer it.
On Wed, Aug 1, 2012 at 2:54 PM, Travis Crawford
wrote:
> Oh interesting - you're saying instead of running a single
> HiveMetaStore thrift service, mos
Oh interesting - you're saying instead of running a single
HiveMetaStore thrift service, most users use the embedded
HiveMetaStore mode and have each CLI instance connect to the DB
directly?
--travis
On Wed, Aug 1, 2012 at 11:47 AM, Edward Capriolo wrote:
> I feel that that interface is very ra
I feel that that interface is very rarely used in the wild. The only
use case I can figure out for it is people with very in depth hive
experience that do not wish to interact with hive through the QL
language. That being said I would think the coverage might be a little
weak there. With the local
I'm using the thrift metastore via TFramedTransport. What value do you
specify for hive.metastore.client.socket.timeout? I'm using 60.
If I open the CLI, run "show tables", wait the timeout period, then
run "show tables" the CLI hangs in:
"main" prio=10 tid=0x4151a000 nid=0x448 runnable [
Are you communicating with a thrift metastore or a JDBC metastore? I
have had connections opened for long periods of time and never
remember experiencing them timeout.
Edward
On Wed, Aug 1, 2012 at 12:01 PM, Travis Crawford
wrote:
> Hey Hive gurus -
>
> Does anyone know how the CLI handles met
Hey Hive gurus -
Does anyone know how the CLI handles metastore connection timeouts? It
seems if I leave a CLI session idle more than
hive.metastore.client.socket.timeout seconds then run "show tables",
the cli hangs for the timeout then throws a SocketTimeoutException.
Restarting the CLI and runn