Re: Question regarding node failure scenario

tionException( > FunctionStreamingResultCollector.java:473) > at org.apache.geode.internal.cache.partitioned. > PRFunctionStreamingResultCollector.getResult( > PRFunctionStreamingResultCollector.java:95) > ... 9 more > > > 3. Per Akihiro's questions: > node N1 a

RE: Question regarding node failure scenario

e Replicated region in the same distributed system? A Geode client updates the data. Thanks Roi -Original Message- From: Michael Stolz [mailto:mst...@pivotal.io] Sent: Monday, July 24, 2017 9:26 PM To: dev@geode.apache.org Subject: Re: Question regarding node failure scenario Wit

Re: Question regarding node failure scenario

Without subscription-redundancy you are running the risk that some of the data isn't being pushed to you in the event of a server failure. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Sun, Jul 23, 2017 at 10:06 PM, Akihiro Kitada

Re: Question regarding node failure scenario

Hello Roi, I want to confirm actual your configuration. >- I have a replicated Node, say N1 and its replicated N2 (N2 gets activated when N1 is down) and they are configured to send updates via continuous query to my process which then reports on these updates. Do node N1 and N2 replicate each

Question regarding node failure scenario

Hi, (Bear with me I am a bit new here :)) I have the following scenario, I wonder if anyone can comment on it - is it a known issue, maybe it was solved already in later version, etc. (I am using version 1.0.0) Or maybe you can point me to somewhere in the code. I have posted this question

Re: Question regarding node failure scenario

How are you performing the updates? Is N1 directly making updates or are they coming from some other source? What is the subscription-redundancy of your client that has registered continuous queries? -Dan On Mon, Jul 3, 2017 at 8:19 AM, Roi Apelker wrote: > Hi, > > I

Question regarding node failure scenario

Hi, I have the following scenario, I wonder if anyone can comment on it - is it a known issue, maybe it was solved already in later version, etc. (I am using version 1.0.0) Bear with me I am a bit new here :) I have a replicated Node, say N1 and its replicated N2 (N2 gets activated when N1