[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1090) Hot Rod protocol improvements for version 2

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612485#comment-12612485 ] 

Galder Zamarreño commented on ISPN-1090:
----------------------------------------

To support virtual nodes more efficiently, the hash topology header must change:
- When virtual nodes are enabled, we're sending host:port information repeated for each of the hash ids belonging to a HotRod server. So, the protocol needs to be more efficient in v2 sending the host:port only once and then N hash ids, where N is the number of configured virtual nodes. If virtual nodes is disabled, the default is 1 virtual node, so N=1.

> Hot Rod protocol improvements for version 2
> -------------------------------------------
>
>                 Key: ISPN-1090
>                 URL: https://issues.jboss.org/browse/ISPN-1090
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Cache Server
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.2.0.Final
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira