incubator-blur-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ravikumar Govindarajan <ravikumar.govindara...@gmail.com>
Subject Re: Thrift non-blocking server removed?
Date Wed, 23 Nov 2016 05:22:53 GMT
Thanks for the clarification...

Our concurrency overhead is quite low. Guess we can safely switch over to
the new model

On Mon, Nov 21, 2016 at 6:38 PM, Aaron McCurry <amccurry@gmail.com> wrote:

> If I remember correctly the biggest reason at the time (not sure if it's
> still true or not) was the non-blocking server didn't support the sasl
> authentication.  Perhaps with newer versions of Thrift this is no longer
> the case.
>
> Aaron
>
> On Mon, Nov 21, 2016 at 4:18 AM, Ravikumar Govindarajan <
> ravikumar.govindarajan@gmail.com> wrote:
>
> > I just saw this commit
> > https://git1-us-west.apache.org/repos/asf?p=incubator-
> > blur.git;a=commitdiff;h=5853d86e
> > where non-blocking server is removed and threaded-server model is used...
> >
> > Are there any particular reasons for this change?
> >
> > The reason why I am asking is, we use non-blocking server mode as of
> today
> > & frequently see responses from controller side (After collating all
> query
> > data from shard-servers etc...) not getting through to the calling VM
> (Our
> > app-servers)
> >
> > We suspect AbstractNonBlockingServer.responseReady() method to be the
> > culprit but not entirely sure.
> >
> > May be changing to threaded-thrift servers will do the trick for us.
> > Anyways, its good to know the actual reason(s) for the change
> >
> > --
> > Ravi
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message