Ok I see. Thanks again! fre 6 okt. 2017 kl. 22:13 skrev Matthias J. Sax <matth...@confluent.io>:
> >> I guess eventually consistent reads might be a reasonable trade off if > you > >> can get ability to serve reads without downtime in some cases. > > Agreed :) > > >> By the way standby replicas are just extra consumers/processors of input > >> topics? Or is there some custom protocol for sinking the state? > > We use a second consumer, that reads the changlog topic (that is written > by the active store) to update the hot standby. > > > -Matthias > > On 10/6/17 1:10 PM, Stas Chizhov wrote: > > Thank you! > > > > I guess eventually consistent reads might be a reasonable trade off if > you > > can get ability to serve reads without downtime in some cases. > > > > By the way standby replicas are just extra consumers/processors of input > > topics? Or is there some custom protocol for sinking the state? > > > > > > > > fre 6 okt. 2017 kl. 20:03 skrev Matthias J. Sax <matth...@confluent.io>: > > > >> No, that is not possible. > >> > >> Note: standby replicas might "lag" behind the active store, and thus, > >> you would get different results if querying standby replicas would be > >> supported. > >> > >> We might add this functionality at some point though -- but there are no > >> concrete plans atm. Contributions are always welcome of course :) > >> > >> > >> -Matthias > >> > >> On 10/6/17 4:18 AM, Stas Chizhov wrote: > >>> Hi > >>> > >>> Is there a way to serve read read requests from standby replicas? > >>> StreamsMeatadata does not seem to provide standby end points as far as > I > >>> can see. > >>> > >>> Thank you, > >>> Stas > >>> > >> > >> > > > >
