[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:
-----------------------------------
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
[JBoss JIRA] (ISPN-7461) Cache is not rebalanced on merge
by Dennis Reed (JIRA)
Dennis Reed created ISPN-7461:
---------------------------------
Summary: 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
[JBoss JIRA] (ISPN-7227) SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-7227?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek updated ISPN-7227:
----------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.CR2)
> SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails
> --------------------------------------------------------------
>
> Key: ISPN-7227
> URL: https://issues.jboss.org/browse/ISPN-7227
> Project: Infinispan
> Issue Type: Bug
> Components: Integration
> Affects Versions: 9.0.0.Alpha4
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
> Fix For: 9.0.0.CR1, 9.0.0.Final
>
>
> {{SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT}} fails with
> {noformat}
> Caused by: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"master.war#pu-master\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"master.war#pu-master\": javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory
> Caused by: org.hibernate.search.exception.SearchException: HSEARCH000103: Unable to initialize IndexManager named 'org.infinispan.test.integration.as.jms.model.RegisteredMember'
> Caused by: org.hibernate.search.exception.SearchException: HSEARCH000252: Unable to initialize directory provider org.infinispan.hibernate.search.spi.InfinispanDirectoryProvider for index org.infinispan.test.integration.as.jms.model.RegisteredMember
> Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml
> Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml
> Caused by: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in UDP are not recognized: {oob_thread_pool.max_threads=200, internal_thread_pool.max_threads=20, internal_thread_pool.keep_alive_time=60000, thread_pool.queue_enabled=false, internal_thread_pool.min_threads=5, oob_thread_pool.keep_alive_time=60000, oob_thread_pool.min_threads=20, oob_thread_pool.queue_enabled=false, internal_thread_pool.queue_max_size=500, internal_thread_pool.queue_enabled=true}"}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7227) SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-7227?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek resolved ISPN-7227.
-----------------------------------
Resolution: Done
> SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails
> --------------------------------------------------------------
>
> Key: ISPN-7227
> URL: https://issues.jboss.org/browse/ISPN-7227
> Project: Infinispan
> Issue Type: Bug
> Components: Integration
> Affects Versions: 9.0.0.Alpha4
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
> Fix For: 9.0.0.Final, 9.0.0.CR1
>
>
> {{SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT}} fails with
> {noformat}
> Caused by: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"master.war#pu-master\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"master.war#pu-master\": javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory
> Caused by: org.hibernate.search.exception.SearchException: HSEARCH000103: Unable to initialize IndexManager named 'org.infinispan.test.integration.as.jms.model.RegisteredMember'
> Caused by: org.hibernate.search.exception.SearchException: HSEARCH000252: Unable to initialize directory provider org.infinispan.hibernate.search.spi.InfinispanDirectoryProvider for index org.infinispan.test.integration.as.jms.model.RegisteredMember
> Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml
> Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml
> Caused by: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in UDP are not recognized: {oob_thread_pool.max_threads=200, internal_thread_pool.max_threads=20, internal_thread_pool.keep_alive_time=60000, thread_pool.queue_enabled=false, internal_thread_pool.min_threads=5, oob_thread_pool.keep_alive_time=60000, oob_thread_pool.min_threads=20, oob_thread_pool.queue_enabled=false, internal_thread_pool.queue_max_size=500, internal_thread_pool.queue_enabled=true}"}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPRK-42) Support for writing using protobuf marshaller to Infinispan
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPRK-42?page=com.atlassian.jira.plugin.s... ]
Gustavo Fernandes updated ISPRK-42:
-----------------------------------
Status: Open (was: New)
> Support for writing using protobuf marshaller to Infinispan
> -----------------------------------------------------------
>
> Key: ISPRK-42
> URL: https://issues.jboss.org/browse/ISPRK-42
> Project: Infinispan Spark
> Issue Type: Enhancement
> Components: RDD
> Affects Versions: 0.4
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 0.5
>
>
> When using {{rdd.writeToInfinispan}} to write an arbitrary (K,V) RDD to Infinispan, the connector will use the default marshaller and doesn't support writing using a protobuf marshaller.
> It should respect the {{infinispan.rdd.query.proto.protoclasses}} or the pair {{infinispan.rdd.query.proto.protofiles/infinispan.rdd.query.proto.marshallers}} to correctly configure the serialization context in order to write to the cache.
> Also, it should have a property to allow auto-registration of the proto files.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month