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 <roi.apel...@amdocs.com> wrote: > 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 is down) and they are configured to send updates via continuous > query to my process which then reports on these updates. > > N1 is working all the time and serves as a server, and data is written to > it continuously. If 1000 events are written to N1, the final report I am > referring to will indicate 1000. > > When N1 gets killed for any reason, sometimes the updates do get to my > reporting process and the report is 100% accurate. > > But sometimes, the report is inaccurate, e.g. after running 1000 events, > my report says 950. > > The fact is, that the report is not accurate, and I only assume that > something is wrong in the update mechanism, somewhere in the area of > continuous query, or somewhere in the replication between the nodes. > > Has anyone encountered something similar and can share a thought? Maybe it > was even solved in a later version? > > Thanks > > Roi > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer < > https://www.amdocs.com/about/email-disclaimer> >
