July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8106) Enable the unused imports checkstyle rule

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8106?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8106: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5318 There's still an issue with references to nested classes/interfaces in javadocs, but it's good enough. > Enable the unused imports checkstyle rule > ----------------------------------------- > > Key: ISPN-8106 > URL: https://issues.jboss.org/browse/ISPN-8106 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 9.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > > Checkstyle 8.1 finally fixes the various problems with the unused imports check: > https://github.com/checkstyle/checkstyle/issues/2840 > https://github.com/checkstyle/checkstyle/issues/4606 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8106) Enable the unused imports checkstyle rule

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8106: ---------------------------------- Summary: Enable the unused imports checkstyle rule Key: ISPN-8106 URL: https://issues.jboss.org/browse/ISPN-8106 Project: Infinispan Issue Type: Task Components: Build process Affects Versions: 9.1.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Priority: Minor Checkstyle 8.1 finally fixes the various problems with the unused imports check: https://github.com/checkstyle/checkstyle/issues/2840 https://github.com/checkstyle/checkstyle/issues/4606 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8106) Enable the unused imports checkstyle rule

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8106?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8106: ------------------------------- Status: Open (was: New) > Enable the unused imports checkstyle rule > ----------------------------------------- > > Key: ISPN-8106 > URL: https://issues.jboss.org/browse/ISPN-8106 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 9.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > > Checkstyle 8.1 finally fixes the various problems with the unused imports check: > https://github.com/checkstyle/checkstyle/issues/2840 > https://github.com/checkstyle/checkstyle/issues/4606 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8092?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8092: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5253 > 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: Dan Berindei > Priority: Minor > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8105) Multimap - Handle names between regular and multimap cache

by Katia Aresti (JIRA)

Katia Aresti created ISPN-8105: ---------------------------------- Summary: Multimap - Handle names between regular and multimap cache Key: ISPN-8105 URL: https://issues.jboss.org/browse/ISPN-8105 Project: Infinispan Issue Type: Enhancement Reporter: Katia Aresti Assignee: Katia Aresti When a multimap cache, embedded or hotrod, is created, there is no check or anything that tags the cache as a multimap cache. So if the cache already exists, this is conflicting. Add a new configuration parameter or a namespace in multimaps to avoid that -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8104) Implement Ansible Service Broker

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-8104: ----------------------------------------- Summary: Implement Ansible Service Broker Key: ISPN-8104 URL: https://issues.jboss.org/browse/ISPN-8104 Project: Infinispan Issue Type: Enhancement Components: Cloud Integrations Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8103) Autogenerate certificates by OpenShift and use them for client/server

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-8103: ----------------------------------------- Summary: Autogenerate certificates by OpenShift and use them for client/server Key: ISPN-8103 URL: https://issues.jboss.org/browse/ISPN-8103 Project: Infinispan Issue Type: Enhancement Components: Cloud Integrations Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8102) Add HOSA to the Infinispan templates

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8102?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-8102: ------------------------------------------- We also need to pick up some valuable metrics. > Add HOSA to the Infinispan templates > ------------------------------------ > > Key: ISPN-8102 > URL: https://issues.jboss.org/browse/ISPN-8102 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8102) Add HOSA to the Infinispan templates

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-8102: ----------------------------------------- Summary: Add HOSA to the Infinispan templates Key: ISPN-8102 URL: https://issues.jboss.org/browse/ISPN-8102 Project: Infinispan Issue Type: Enhancement Components: Cloud Integrations Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8101) Identify how Service Catalog plans will be used

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-8101: ----------------------------------------- Summary: Identify how Service Catalog plans will be used Key: ISPN-8101 URL: https://issues.jboss.org/browse/ISPN-8101 Project: Infinispan Issue Type: Enhancement Components: Cloud Integrations Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec The Plan field shall be used as tier. The question is what type of hierarchy would we like to built with it? Perhaps the plan should indicate the cluster size: small/medium/big? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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