Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question

what's the behavior while notifying about changed data to slow nodes?

Notifying clients about changed data and maintaining data ordering are challenges for other distributed data management solutions that support client-side interfaces. Any JSR 107/JCache system—such as Ehcache, Terracotta or Coherence—faces the problem of what to do when a client is slow to receive data. Causes of this condition include JVM pauses, network-adapter issues and high data flow that the system cannot keep up with.

Does Gigaspaces disconnect such clients from the system or slow all clients down to the speed of the slowest client?

I didn't find anything related to this in gigaspace documentation.

{quote}This thread was imported from the previous forum. For your reference, the original is [available here|http://forum.openspaces.org/thread.jspa?threadID=3883]{quote}

asked 2012-07-09 10:41:34 -0500

ankit gravatar image

updated 2013-08-08 09:52:00 -0500

jaissefsfex gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2012-07-09 11:17:45 -0500

shay hassidim gravatar image
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2012-07-09 10:41:34 -0500

Seen: 29 times

Last updated: Jul 09 '12