Loading...

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

This JIRA will act as a place to keep track of enhancements to the Hot Rod protocol that should be included in version 2 of the protocol:

We need a new error status code so that clients can detect when a node has been suspected and so react accordingly (i.e. not bubble it up but instead failover). Currently, this can be solved by checking whether the error message contains SuspectException but this is not nice.
Since we're not gonna be supporting asymmetric clusters in the mean time, we need a new error status code to deal with situations where the cache is not defined in the server. Currently we check for CacheNotFoundException in the message but that's not nice.

duplicates

ISPN-3533 Design HotRod protocol version 2.0

incorporates

ISPN-1855 Accessing a non-distributed cache from a RemoteCacheManager can break topology updates

ISPN-484 Querying over HotRod

ISPN-374 Add event handling to Hot Rod

ISPN-1293 Enable default lifespan/maxIdle values to be used by the Hot Rod server

is related to

ISPN-1217 Implement Virtual Nodes for Hotrod Client Server

relates to

ISPN-4717 Hot Rod 2.0 should add error codes for suspected nodes and stopping/stopped caches

ISPN-1111 SuspectException should expose the suspected member

(1 is related to, 2 relates to)