n(
> FunctionStreamingResultCollector.java:473)
> at org.apache.geode.internal.cache.partitioned.
> PRFunctionStreamingResultCollector.getResult(
> PRFunctionStreamingResultCollector.java:95)
> ... 9 more
>
>
> 3. Per Akihiro's questions:
> node N1 and N2
e same 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
Wi
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 wrote:
> Hello Roi,
>
>
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 d
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 have the following scenari
