[infinispan-issues] [JBoss JIRA] (ISPN-1965) Some entries not available during view change

[Michal Linhard (JIRA)]

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

Michal Linhard commented on ISPN-1965:
--------------------------------------

As you can see here, hyperion hosts have two interfaces: https://docspace.corp.redhat.com/docs/DOC-93047
>From the IPs used in the tests you can see that all of them are mapped to eth0 now.
                
> Some entries not available during view change
> ---------------------------------------------
>
>                 Key: ISPN-1965
>                 URL: https://issues.jboss.org/browse/ISPN-1965
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.1.3.FINAL
>            Reporter: Michal Linhard
>            Assignee: Dan Berindei
>
> In the 4 node, dist mode, num-owners=2, elasticity test
> http://www.qa.jboss.com/~mlinhard/hyperion/run44-elas-dist/
> there is a cca 90 sec period of time where clients get null responses to GET
> requests on entries that should exist in the cache.
> first occurence:
> hyperion1139.log 05:31:01,202 286.409
> last occurence:
> hyperion1135.log 05:32:45,441 390.648
> total occurence count: (in all 19 driver nodes)
> 152241
> (this doesn't mean it happens for 152K keys, because each key is retried after
> erroneous attempt)
> data doesn't seem to be lost, because these errors cease after a while and
> number of entries returns back to normal (see cache_entries.csv)
> this happens approximately in the period between node0001 is killed and cluster
> {node0002 - node0004} is formed (and shortly after).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira