]
Michal Linhard commented on ISPN-3149:
--------------------------------------
yup, I forgot to add: this happens at the beginning of my test, so the scenario is
basically: start 4 nodes in dist_sync mode owners=2 with testCache containing no data at
all and this happens, therefore I consider it unexpected - there should be no state
transfer at all.
And btw isn't this strange that node01 is processing initial cache topology 0 ?
It's natural that StateConsumerImpl.findSource won't find any sources since
it's the only node in the cluster.
Unexpected reporting of no live owners
--------------------------------------
Key: ISPN-3149
URL:
https://issues.jboss.org/browse/ISPN-3149
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 5.3.0.Beta2
Reporter: Michal Linhard
Assignee: Mircea Markus
Running a four node test with infinispan-server 5.3.0-SNAPSHOT
produces following errors:
{code}
08:46:22,962 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service
thread 1-3) Starting StateTransferManager of cache testCache on node node01/default
08:46:22,969 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service
thread 1-3) Installing new cache topology CacheTopology{id=0,
currentCH=DefaultConsistentHash{numSegments=40, numOwners=2, members=[node01/default]},
pendingCH=null} on cache testCache
08:46:22,972 TRACE [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) Received new topology for cache testCache, isRebalance = false, isMember = true,
topology = CacheTopology{id=0, currentCH=DefaultConsistentHash{numSegments=40,
numOwners=2, members=[node01/default]}, pendingCH=null}
08:46:22,972 TRACE [org.infinispan.statetransfer.StateTransferLockImpl] (MSC service
thread 1-3) Signalling topology 0 is installed
08:46:22,973 TRACE [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) On cache testCache we have: added segments: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15, 17, 16, 19, 18, 21, 20, 23, 22, 25, 24, 27, 26, 29, 28, 31, 30, 34, 35,
32, 33, 38, 39, 36, 37]
08:46:22,974 DEBUG [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) Adding inbound state transfer for segments [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 14, 15, 17, 16, 19, 18, 21, 20, 23, 22, 25, 24, 27, 26, 29, 28, 31, 30, 34, 35, 32,
33, 38, 39, 36, 37] of cache testCache
08:46:22,974 ERROR [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) ISPN000208: No live owners found for segment 0 of cache testCache. Current owners
are: [node01/default]. Faulty owners: []
08:46:22,975 ERROR [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) ISPN000208: No live owners found for segment 1 of cache testCache. Current owners
are: [node01/default]. Faulty owners: []
08:46:22,976 ERROR [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) ISPN000208: No live owners found for segment 2 of cache testCache. Current owners
are: [node01/default]. Faulty owners: []
08:46:22,976 ERROR [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) ISPN000208: No live owners found for segment 3 of cache testCache. Current owners
are: [node01/default]. Faulty owners: []
08:46:22,977 ERROR [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) ISPN000208: No live owners found for segment 4 of cache testCache. Current owners
are: [node01/default]. Faulty owners: []
08:46:22,977 ERROR [org.infinispan.statetransfer.StateConsumerImpl] (MSC service thread
1-3) ISPN000208: No live owners found for segment 5 of cache testCache. Current owners
are:
{code}
all logs:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/user/mlinhard@REDHAT.COM...
configs:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/user/mlinhard@REDHAT.COM...
infinispan-server build info:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/user/mlinhard@REDHAT.COM...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: