February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-7462) Administration console - server in reload-required state is not working correctly

by Roman Macor (JIRA)

Roman Macor created ISPN-7462: --------------------------------- Summary: Administration console - server in reload-required state is not working correctly Key: ISPN-7462 URL: https://issues.jboss.org/browse/ISPN-7462 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.0.0.CR1 Reporter: Roman Macor Click on cache-container -> configuration -> change value (e.g. Min Threads) -> Save -> Restart Later -> click on clusters tab -> cluster -> server Issues: - Server has status RELOAD-REQUIRED, I suggest we change it to RESTART-REQUIRED. - Cluster has status STARTED, it should also be RESTART-REQUIRED/RELOAD-REQUIRED - Server has enabled start button and disabled stop button -> it should be the other way around -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7432) Cassandra cache store doesn't work with byte array keys

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7432?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7432: ----------------------------------- Fix Version/s: 9.0.0.Final > Cassandra cache store doesn't work with byte array keys > ------------------------------------------------------- > > Key: ISPN-7432 > URL: https://issues.jboss.org/browse/ISPN-7432 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Jakub Markos > Assignee: Jakub Markos > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7432) Cassandra cache store doesn't work with byte array keys

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7432?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7432: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cassandra cache store doesn't work with byte array keys > ------------------------------------------------------- > > Key: ISPN-7432 > URL: https://issues.jboss.org/browse/ISPN-7432 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Jakub Markos > Assignee: Jakub Markos > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7052) Cassandra cache store: replication parameters configurable

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7052?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7052: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Cassandra cache store: replication parameters configurable > ---------------------------------------------------------- > > Key: ISPN-7052 > URL: https://issues.jboss.org/browse/ISPN-7052 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Антон Борисов > Assignee: Jakub Markos > Fix For: 9.0.0.Final > > > * Make possible to set replication strategy class and its parameters as it described here: > https://docs.datastax.com/en/cql/3.1/cql/cql_reference/create_keyspace_r.... > Now the hard-coded value is used: > {noformat} session.execute("CREATE KEYSPACE IF NOT EXISTS " + configuration.keyspace() + " WITH replication " + > "= {'class':'SimpleStrategy', 'replication_factor':1};");{noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7053) Cassandra cache store: consistency levels separate configuration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7053?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7053: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Cassandra cache store: consistency levels separate configuration > ---------------------------------------------------------------- > > Key: ISPN-7053 > URL: https://issues.jboss.org/browse/ISPN-7053 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Антон Борисов > Assignee: Jakub Markos > Fix For: 9.0.0.Final > > > Need to have ability to set write and read consistency levels separately. > https://docs.datastax.com/en/cassandra/2.0/cassandra/dml/dml_config_consi... > according to the type of operation appropriate level should be set to PreparedStatement object. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7054) Cassandra cache store: compression support

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7054?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7054: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Cassandra cache store: compression support > ------------------------------------------ > > Key: ISPN-7054 > URL: https://issues.jboss.org/browse/ISPN-7054 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Антон Борисов > Assignee: Jakub Markos > Fix For: 9.0.0.Final > > > Add possibility to configure data compression as it described here: > https://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_confi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7055) Cassandra cache store: SSL support

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7055?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7055: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Cassandra cache store: SSL support > ---------------------------------- > > Key: ISPN-7055 > URL: https://issues.jboss.org/browse/ISPN-7055 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Антон Борисов > Assignee: Jakub Markos > Fix For: 9.0.0.Final > > > Add possibility to configure SSL using e.g. > com.datastax.driver.core.SSLOptions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7056) Cassandra cache store: credentials support

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7056?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7056: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Cassandra cache store: credentials support > ------------------------------------------ > > Key: ISPN-7056 > URL: https://issues.jboss.org/browse/ISPN-7056 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Антон Борисов > Assignee: Jakub Markos > Fix For: 9.0.0.Final > > > Add configurable username and password for cassandra user -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7461) Cache is not rebalanced on merge

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/ISPN-7461?page=com.atlassian.jira.plugin.... ] Dennis Reed edited comment on ISPN-7461 at 2/11/17 8:51 PM: ------------------------------------------------------------ Rebalancing is done in DefaultRebalancePolicy#updateCacheStatus, which (incorrectly) skips the rebalance after a merge because of: if (!cacheStatus.hasJoiners() && isBalanced(cacheStatus.getCacheTopology().getCurrentCH())) { ClusterTopologyManagerImpl#updateCacheStatusAfterMerge is setting the CH to the current merged member list, and the union of all CHs, which makes ClusterCacheStatus.hasJoiners return false. isBalanced only checks if each owner has the correct number of segments, not that it's evenly distributed. was (Author: dereed): Rebalancing is done in DefaultRebalancePolicy#updateCacheStatus, which skips the rebalance during a merge because of: if (!cacheStatus.hasJoiners() && isBalanced(cacheStatus.getCacheTopology().getCurrentCH())) { ClusterTopologyManagerImpl#updateCacheStatusAfterMerge is setting the CH to the current merged member list, and the union of all CHs, which makes ClusterCacheStatus.hasJoiners return false. isBalanced only checks if each owner has the correct number of segments, not that it's evenly distributed. > Cache is not rebalanced on merge > -------------------------------- > > Key: ISPN-7461 > URL: https://issues.jboss.org/browse/ISPN-7461 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 5.2.7.Final > Reporter: Dennis Reed > > After a cluster split and merge, the consistent hash is not balanced between the members. > For example in a 2-member cluster, after the merge one node will be primary owner of every segment. In In a larger cluster, some nodes will not own any data. > DefaultConsistentHash{numSegments=60, numOwners=2, members=[RehashAfterPartitionMergeTest-NodeB-49100, RehashAfterPartitionMergeTest-NodeA-11552]} -- 0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, 24: 0 1, 25: 0 1, 26: 0 1, 27: 0 1, 28: 0 1, 29: 0 1, 30: 0 1, 31: 0 1, 32: 0 1, 33: 0 1, 34: 0 1, 35: 0 1, 36: 0 1, 37: 0 1, 38: 0 1, 39: 0 1, 40: 0 1, 41: 0 1, 42: 0 1, 43: 0 1, 44: 0 1, 45: 0 1, 46: 0 1, 47: 0 1, 48: 0 1, 49: 0 1, 50: 0 1, 51: 0 1, 52: 0 1, 53: 0 1, 54: 0 1, 55: 0 1, 56: 0 1, 57: 0 1, 58: 0 1, 59: 0 1 > This is triggered consistently by the RehashAfterPartitionMergeTest test case, but is not caught because it does not sufficiently check the consistent hash. (it checks RebalancePolicy.isBalanced, which merely makes sure each segment has the correct number of owners, not that it's evenly distributed). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7461) Cache is not rebalanced on merge

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/ISPN-7461?page=com.atlassian.jira.plugin.... ] Dennis Reed commented on ISPN-7461: ----------------------------------- ClusterTopologyManagerImpl was substantially rewritten in 7.0. I am not able to reproduce this issue in the latest versions. > Cache is not rebalanced on merge > -------------------------------- > > Key: ISPN-7461 > URL: https://issues.jboss.org/browse/ISPN-7461 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 5.2.7.Final > Reporter: Dennis Reed > > After a cluster split and merge, the consistent hash is not balanced between the members. > For example in a 2-member cluster, after the merge one node will be primary owner of every segment. In In a larger cluster, some nodes will not own any data. > DefaultConsistentHash{numSegments=60, numOwners=2, members=[RehashAfterPartitionMergeTest-NodeB-49100, RehashAfterPartitionMergeTest-NodeA-11552]} -- 0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, 24: 0 1, 25: 0 1, 26: 0 1, 27: 0 1, 28: 0 1, 29: 0 1, 30: 0 1, 31: 0 1, 32: 0 1, 33: 0 1, 34: 0 1, 35: 0 1, 36: 0 1, 37: 0 1, 38: 0 1, 39: 0 1, 40: 0 1, 41: 0 1, 42: 0 1, 43: 0 1, 44: 0 1, 45: 0 1, 46: 0 1, 47: 0 1, 48: 0 1, 49: 0 1, 50: 0 1, 51: 0 1, 52: 0 1, 53: 0 1, 54: 0 1, 55: 0 1, 56: 0 1, 57: 0 1, 58: 0 1, 59: 0 1 > This is triggered consistently by the RehashAfterPartitionMergeTest test case, but is not caught because it does not sufficiently check the consistent hash. (it checks RebalancePolicy.isBalanced, which merely makes sure each segment has the correct number of owners, not that it's evenly distributed). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2017