Lars, Thanks for the pointer, its indeed interesting way. Two follow up questions :
1. Author states "Rather than a separate process, it can be *advantageous * in some situations for each RegionServer to embed their own ThriftServer" , do you happen to have insights on what are those situations? 2. Could there be a situation / application_use_case where HBASE-4460 prove to be unfavorable to an extent where it impacts region server's performance? On Wed, Aug 1, 2012 at 9:19 PM, lars hofhansl <[email protected]> wrote: > There is a little documented feature that Jonathan Gray added a while > back: Running a thrift server as a thread as part of each region server. > This is enabled by settting hbase.regionserver.export.thrift to true in > your configuration. > > While I have not personally tried it, it looks like a fairly lightweight > approach and does not add to the monitoring overhead. > > This is the jira: HBASE-4460. This is only available in 0.94+ (0.94.1 > should be out soon). > > > -- Lars > > > > ----- Original Message ----- > From: Eric <[email protected]> > To: [email protected] > Cc: > Sent: Tuesday, July 31, 2012 4:32 AM > Subject: Where to run Thrift > > I'm currently running thrift on all region server nodes. The reasoning is > that you can run jobs on this cluster and these jobs, when using thrift, > can connect to localhost. > The drawback is that I'm running lots of thrift daemons of course which all > need to be monitored. > > An alternative would be to create one or more dedicated Thrift / REST nodes > which have high specs (raid, etc.). Possible with a load balancer in front > of them. What would you guys recommend? > >
