That's right, round robin should only be applied when you start answering
some client request and stick to it until you're done.
On Fri, Dec 6, 2013 at 9:17 PM, Varun Sharma <[EMAIL PROTECTED]> wrote:
> Hi everyone,
> I have a question about the hbase thrift server and running scans in
> particular. The thrift server maintains a map of <int> -> ResultScanner(s).
> These integers are passed back to the client. Now in a typical setting
> people run many thrift servers and round robin rpc(s) to them.
> It seems that for scans, such a technique of just round robinning is simply
> not going to work. If a scan integer ID has been retrieved from a certain
> thrift server A, all the next() calls and close calls should fall on that
> I just wanted to make sure I got this thinking right and there isn't really
> a way around this because scans, unlike gets have associated state.
> Thanks !