July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8092) Scattered cache state transfer misses segments

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8092: ---------------------------------- Summary: Scattered cache state transfer misses segments Key: ISPN-8092 URL: https://issues.jboss.org/browse/ISPN-8092 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.1.0.Final Reporter: Dan Berindei Assignee: Radim Vansa Priority: Critical I noticed this in the pull request for [ISPN-7997|https://github.com/infinispan/infinispan/pull/5253], which uses a {{ControlledConsistentHashFactory}} to make the stream tests more predictable. For simplicity, I used 3 segments, and the ownership is as follows: * With a full cluster ABC, A owns segment 0, B owns segment 1, and C owns segment 2 * With a smaller cluster A, AB, or AC, A owns all the segments. {{ScatteredStreamIteratorTest.verifyNodeLeavesAfterSendingBackSomeData[SCATTERED_SYNC, tx=false]}} kills node B, and A immediately becomes the owner of segment 1. Then the rebalance starts and A pushes segment 2 to node C, but it doesn't try to fetch any entries from segment 1 that were backed up on node C. {noformat} 17:35:09,897 DEBUG (remote-thread-test-NodeA-p2-t5:[testCache]) [ClusterTopologyManagerImpl] Updating cluster-wide current topology for cache testCache, topology = CacheTopology{id=7, rebalanceId=4, currentCH=ScatteredConsistentHash{ns=3, rebalanced=true, owners = (3)[test-NodeA-59810: 1, test-NodeB-37315: 1, test-NodeC-50539: 1]}, pendingCH=null, unionCH=null, phase=NO_REBALANCE, actualMembers=[test-NodeA-59810, test-NodeB-37315, test-NodeC-50539], persistentUUIDs=[6118c3ba-840e-4838-a0cf-1165d3d5ec4b, 38cc2bd9-0a21-4020-97ab-909a32506fa1, 6a4f1a13-0fbb-4f92-867e-64068d574d4d]}, availability mode = AVAILABLE 17:35:10,974 DEBUG (remote-thread-test-NodeA-p2-t5:[testCache]) [ClusterTopologyManagerImpl] Updating cluster-wide current topology for cache testCache, topology = CacheTopology{id=8, rebalanceId=4, currentCH=ScatteredConsistentHash{ns=3, rebalanced=false, owners = (2)[test-NodeA-59810: 2, test-NodeC-50539: 1]}, pendingCH=null, unionCH=null, phase=NO_REBALANCE, actualMembers=[test-NodeA-59810, test-NodeC-50539], persistentUUIDs=[6118c3ba-840e-4838-a0cf-1165d3d5ec4b, 6a4f1a13-0fbb-4f92-867e-64068d574d4d]}, availability mode = AVAILABLE 17:35:10,975 TRACE (transport-thread-test-NodeA-p4-t2:[Topology-testCache]) [StateConsumerImpl] On cache testCache we have: new segments: [0, 1]; old segments: [0] 17:35:10,975 TRACE (transport-thread-test-NodeA-p4-t2:[Topology-testCache]) [StateConsumerImpl] On cache testCache we have: added segments: {1}; removed segments: {} 17:35:10,975 TRACE (transport-thread-test-NodeA-p4-t2:[Topology-testCache]) [StateConsumerImpl] This is not a rebalance, not doing anything... 17:35:10,976 INFO (remote-thread-test-NodeA-p2-t5:[testCache]) [CLUSTER] ISPN000310: Starting cluster-wide rebalance for cache testCache, topology CacheTopology{id=9, rebalanceId=5, currentCH=ScatteredConsistentHash{ns=3, rebalanced=false, owners = (2)[test-NodeA-59810: 2, test-NodeC-50539: 1]}, pendingCH=ScatteredConsistentHash{ns=3, rebalanced=true, owners = (2)[test-NodeA-59810: 3, test-NodeC-50539: 0]}, unionCH=null, phase=TRANSITORY, actualMembers=[test-NodeA-59810, test-NodeC-50539], persistentUUIDs=[6118c3ba-840e-4838-a0cf-1165d3d5ec4b, 6a4f1a13-0fbb-4f92-867e-64068d574d4d]} 17:35:10,977 TRACE (transport-thread-test-NodeA-p4-t3:[Topology-testCache]) [CacheTopology] Current consistent hash's routing table: 0: 0, 1: 0, 2: 1 17:35:10,977 TRACE (transport-thread-test-NodeA-p4-t3:[Topology-testCache]) [CacheTopology] Pending consistent hash's routing table: 0: 0, 1: 0, 2: 0 17:35:10,978 TRACE (transport-thread-test-NodeA-p4-t3:[Topology-testCache]) [ScatteredVersionManager] Node will transfer value for topology 9 17:35:10,978 TRACE (transport-thread-test-NodeA-p4-t3:[Topology-testCache]) [StateConsumerImpl] On cache testCache we have: new segments: [0, 1, 2]; old segments: [0, 1] 17:35:10,978 TRACE (transport-thread-test-NodeA-p4-t3:[Topology-testCache]) [StateConsumerImpl] On cache testCache we have: added segments: {2}; removed segments: {} 17:35:10,979 TRACE (transport-thread-test-NodeA-p4-t3:[Topology-testCache]) [JGroupsTransport] test-NodeA-59810 sending request 9 to all: StateRequestCommand{cache=testCache, origin=test-NodeA-59810, type=CONFIRM_REVOKED_SEGMENTS, topologyId=9, segments=null} 17:35:10,989 TRACE (transport-thread-test-NodeA-p4-t3:[Topology-testCache]) [StateProviderImpl] Segments to replicate and invalidate: [0, 1] 17:35:10,989 TRACE (transport-thread-test-NodeA-p4-t1:[]) [OutboundTransferTask] Sending last chunk to node test-NodeC-50539 containing 0 cache entries from segments [0, 1] 17:35:10,989 TRACE (stateTransferExecutor-thread-test-NodeA-p7-t1:[StateRequest-testCache]) [RpcManagerImpl] test-NodeA-59810 invoking StateRequestCommand{cache=testCache, origin=test-NodeA-59810, type=START_KEYS_TRANSFER, topologyId=9, segments={2}} to recipient list [test-NodeC-50539] with options RpcOptions{timeout=240000, unit=MILLISECONDS, deliverOrder=NONE, responseFilter=null, responseMode=SYNCHRONOUS_IGNORE_LEAVERS} 17:35:11,017 INFO (transport-thread-test-NodeA-p4-t4:[testCache]) [CLUSTER] ISPN000336: Finished cluster-wide rebalance for cache testCache, topology id = 9 17:35:11,017 DEBUG (transport-thread-test-NodeA-p4-t4:[testCache]) [ClusterTopologyManagerImpl] Updating cluster-wide current topology for cache testCache, topology = CacheTopology{id=10, rebalanceId=5, currentCH=ScatteredConsistentHash{ns=3, rebalanced=true, owners = (2)[test-NodeA-59810: 3, test-NodeC-50539: 0]}, pendingCH=null, unionCH=null, phase=NO_REBALANCE, actualMembers=[test-NodeA-59810, test-NodeC-50539], persistentUUIDs=[6118c3ba-840e-4838-a0cf-1165d3d5ec4b, 6a4f1a13-0fbb-4f92-867e-64068d574d4d]}, availability mode = AVAILABLE {noformat} {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7642) Administration console - remote sites are not displayed correctly on cache container page

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7642?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7642: -------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/218 > Administration console - remote sites are not displayed correctly on cache container page > ----------------------------------------------------------------------------------------- > > Key: ISPN-7642 > URL: https://issues.jboss.org/browse/ISPN-7642 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot-cacheContainer.png, Screenshot-detail-cache.png, clustered.xml > > > Have 2 caches each configured with a different remote site. > When you click on cache container, both remote sites are displayed on both cache cards. Clicking on a cache to see cache detail page shows correct remote site. Please see the attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7642) Administration console - remote sites are not displayed correctly on cache container page

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7642?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7642: ------------------------------------ [~vblagojevic]Makes sense to me. If we have a large number of caches the page would become unresponsive. > Administration console - remote sites are not displayed correctly on cache container page > ----------------------------------------------------------------------------------------- > > Key: ISPN-7642 > URL: https://issues.jboss.org/browse/ISPN-7642 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot-cacheContainer.png, Screenshot-detail-cache.png, clustered.xml > > > Have 2 caches each configured with a different remote site. > When you click on cache container, both remote sites are displayed on both cache cards. Clicking on a cache to see cache detail page shows correct remote site. Please see the attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7642) Administration console - remote sites are not displayed correctly on cache container page

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7642?page=com.atlassian.jira.plugin.... ] Ryan Emerson edited comment on ISPN-7642 at 7/24/17 11:01 AM: -------------------------------------------------------------- [~vblagojevic]Makes sense to me. If we have a large number of caches the page would become unresponsive otherwise. was (Author: ryanemerson): [~vblagojevic]Makes sense to me. If we have a large number of caches the page would become unresponsive. > Administration console - remote sites are not displayed correctly on cache container page > ----------------------------------------------------------------------------------------- > > Key: ISPN-7642 > URL: https://issues.jboss.org/browse/ISPN-7642 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot-cacheContainer.png, Screenshot-detail-cache.png, clustered.xml > > > Have 2 caches each configured with a different remote site. > When you click on cache container, both remote sites are displayed on both cache cards. Clicking on a cache to see cache detail page shows correct remote site. Please see the attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7642) Administration console - remote sites are not displayed correctly on cache container page

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7642?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7642: ------------------------------------------- [~ryanemerson] [~rmacor] I investigated this issue and the problem is the following: cache container structure loaded in the cache container page (list of all caches) does not contain data on per cache level related to backup sites (on cache level) but rather only on container level. Currently, we display backup sites on container level. On per cache page we display cache backup sites correctly because we fetch relevant data on cache level. Having a proper solution i.e. each cache card on container page listing its own backups would require fetching per cache data on cache container page. This, in turn, could be resource intensive (think hundreds of caches). I recommend we only display cache backup icon on each individual cache card on container page (if a cache has backup) and the list of actual backups once the cache page is loaded (the current approach). Thoughts? > Administration console - remote sites are not displayed correctly on cache container page > ----------------------------------------------------------------------------------------- > > Key: ISPN-7642 > URL: https://issues.jboss.org/browse/ISPN-7642 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot-cacheContainer.png, Screenshot-detail-cache.png, clustered.xml > > > Have 2 caches each configured with a different remote site. > When you click on cache container, both remote sites are displayed on both cache cards. Clicking on a cache to see cache detail page shows correct remote site. Please see the attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7642) Administration console - remote sites are not displayed correctly on cache container page

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7642?page=com.atlassian.jira.plugin.... ] Work on ISPN-7642 started by Vladimir Blagojevic. ------------------------------------------------- > Administration console - remote sites are not displayed correctly on cache container page > ----------------------------------------------------------------------------------------- > > Key: ISPN-7642 > URL: https://issues.jboss.org/browse/ISPN-7642 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot-cacheContainer.png, Screenshot-detail-cache.png, clustered.xml > > > Have 2 caches each configured with a different remote site. > When you click on cache container, both remote sites are displayed on both cache cards. Clicking on a cache to see cache detail page shows correct remote site. Please see the attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7919) Expose ResponseCollector in the RpcManager interface

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7919?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7919: ------------------------------- Description: ISPN-6971/https://github.com/infinispan/infinispan/pull/5143 introduces a {{ResponseCollector}} interface in the {{Transport}} interface, the {{RpcManager}} interface should expose it as well (replacing {{ResponseFilter}}). Additionally, we should change core users of {{RpcManager}}/{{JGroupsTransport}} to avoid creating a {{Map<Address, Response>}} as much as possible. was: ISPN-6971/https://github.com/infinispan/infinispan/pull/5143 introduces a `ResponseCollector` interface in the `Transport` interface, the `RpcManager` interface should expose it as well (replacing `ResponseFilter`). Additionally, we should change core users of `RpcManager`/`JGroupsTransport` to avoid creating a `Map<Address, Response>` as much as possible. > Expose ResponseCollector in the RpcManager interface > ---------------------------------------------------- > > Key: ISPN-7919 > URL: https://issues.jboss.org/browse/ISPN-7919 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Final > > > ISPN-6971/https://github.com/infinispan/infinispan/pull/5143 introduces a {{ResponseCollector}} interface in the {{Transport}} interface, the {{RpcManager}} interface should expose it as well (replacing {{ResponseFilter}}). > Additionally, we should change core users of {{RpcManager}}/{{JGroupsTransport}} to avoid creating a {{Map<Address, Response>}} as much as possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7919) Expose ResponseCollector in the RpcManager interface

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7919?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7919: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5315 > Expose ResponseCollector in the RpcManager interface > ---------------------------------------------------- > > Key: ISPN-7919 > URL: https://issues.jboss.org/browse/ISPN-7919 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Final > > > ISPN-6971/https://github.com/infinispan/infinispan/pull/5143 introduces a `ResponseCollector` interface in the `Transport` interface, the `RpcManager` interface should expose it as well (replacing `ResponseFilter`). > Additionally, we should change core users of `RpcManager`/`JGroupsTransport` to avoid creating a `Map<Address, Response>` as much as possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7865) Distributed Stream thread usage for key aware operations can be improved

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7865?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7865: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/5283, https://github.com/infinispan/infinispan/pull/5314 (was: https://github.com/infinispan/infinispan/pull/5283) > Distributed Stream thread usage for key aware operations can be improved > ------------------------------------------------------------------------ > > Key: ISPN-7865 > URL: https://issues.jboss.org/browse/ISPN-7865 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Final > > > Currently iterator will block a thread on the remote server when it is trying to send back a response. It would be better if we used full async API to instead request blocks of values as the iterator consumes them. We should make sure we always maintain a distributed batch size worth. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8091) Do not publish uberjars to Maven

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-8091: ------------------------------------- Summary: Do not publish uberjars to Maven Key: ISPN-8091 URL: https://issues.jboss.org/browse/ISPN-8091 Project: Infinispan Issue Type: Bug Components: Core Reporter: Tristan Tarrant Assignee: Sebastian Łaskawiec Fix For: 9.2.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2017