August 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8240) Coordinator sends REBALANCE_START command when there is already a rebalance in progress

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8240?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8240: ------------------------------- Status: Open (was: New) > Coordinator sends REBALANCE_START command when there is already a rebalance in progress > --------------------------------------------------------------------------------------- > > Key: ISPN-8240 > URL: https://issues.jboss.org/browse/ISPN-8240 > Project: Infinispan > Issue Type: Bug > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > > Normally the {{REBALANCE_START}} command should only be sent at the start of a rebalance, and any topology updates sent before all the nodes confirm the rebalance phase should have {{CH_UPDATE}}. > Since the change to 4 phases, this is no longer true: first {{ClusterCacheStatus.updateTopologyMembers}} first clears the {{RebalanceConfirmationCollector}}, then it broadcasts a {{CH_UPDATE}}. Then {{queueRebalance}} immediately creates a new {{RCC}} and broadcasts a {{REBALANCE_START}}, instead of waiting for the current rebalance to finish. > I propose we remove {{REBALANCE_START}}, as it was just a crude version of {{CacheTopology.Phase}}. We should also remove the {{isRebalance}} parameter from {{StateConsumerImpl.onTopologyUpdate()}}. > I'm still not sure if rebalancing the pending CH immediately is ok. On the one hand, I would like the rebalance to finish with {{updateMembers(union(currentCH, pendingCH))}} as the new pending CH, so that segments that were already transferred keep an extra copy. On the other hand, that would only help for segments that have at least on owner in the current CH: if the current CH has 0 owners and {{updateMembers}} allocates new ones, those new owners won't request data from the pending CH owners anyway. Fixing that case would require the coordinator to fetch the transfer status from all the nodes before removing a node from the topology. But if the coordinator knew exactly which segments were transferred, it could finish the rebalance immediately and start a new one -- so it would be more similar to the current approach. > Note: the {{SyncConsistentHashFactory}} allocation is not 100% stable, even when nodes are not added, so A ∈ owners(segment) in topology ABCD does not guarantee that A ∈ owners(segment) in topology ABC. But it should be good enough to keep A an owner in 90% of the cases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8243) Embedded server tests not using PrivateGlobalConfiguration serverMode

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8243?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8243: ------------------------------------ Component/s: Test Suite - Query Test Suite - Server > Embedded server tests not using PrivateGlobalConfiguration serverMode > --------------------------------------------------------------------- > > Key: ISPN-8243 > URL: https://issues.jboss.org/browse/ISPN-8243 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query, Test Suite - Server > Affects Versions: 9.1.0.Final > Reporter: Gustavo Fernandes > > When starting the infinispan server as a separate process, the following setting is applied to the cache manager: > {code:java} > GlobalConfigurationBuilder builder = ... > builder.addModule(PrivateGlobalConfigurationBuilder.class).serverMode(true) > {code} > But the server tests that runs in embedded mode (when starting the server directly via HotRodServer class) do not apply this setting. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8243) Embedded server tests not using PrivateGlobalConfiguration serverMode

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8243?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8243: ------------------------------------ Affects Version/s: 9.1.0.Final > Embedded server tests not using PrivateGlobalConfiguration serverMode > --------------------------------------------------------------------- > > Key: ISPN-8243 > URL: https://issues.jboss.org/browse/ISPN-8243 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query, Test Suite - Server > Affects Versions: 9.1.0.Final > Reporter: Gustavo Fernandes > > When starting the infinispan server as a separate process, the following setting is applied to the cache manager: > {code:java} > GlobalConfigurationBuilder builder = ... > builder.addModule(PrivateGlobalConfigurationBuilder.class).serverMode(true) > {code} > But the server tests that runs in embedded mode (when starting the server directly via HotRodServer class) do not apply this setting. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8243) Embedded server tests not using PrivateGlobalConfiguration serverMode

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8243?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-8243: --------------------------------------- Assignee: Gustavo Fernandes > Embedded server tests not using PrivateGlobalConfiguration serverMode > --------------------------------------------------------------------- > > Key: ISPN-8243 > URL: https://issues.jboss.org/browse/ISPN-8243 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query, Test Suite - Server > Affects Versions: 9.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > When starting the infinispan server as a separate process, the following setting is applied to the cache manager: > {code:java} > GlobalConfigurationBuilder builder = ... > builder.addModule(PrivateGlobalConfigurationBuilder.class).serverMode(true) > {code} > But the server tests that runs in embedded mode (when starting the server directly via HotRodServer class) do not apply this setting. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8243) Embedded server tests not using PrivateGlobalConfiguration serverMode

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8243?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8243: ------------------------------------ Description: When starting the infinispan server as a separate process, the following setting is applied to the cache manager: {code:java} GlobalConfigurationBuilder builder = ... builder.addModule(PrivateGlobalConfigurationBuilder.class).serverMode(true) {code} But the server tests that run in embedded mode (when starting the server directly via HotRodServer class) do not apply this setting. was: When starting the infinispan server as a separate process, the following setting is applied to the cache manager: {code:java} GlobalConfigurationBuilder builder = ... builder.addModule(PrivateGlobalConfigurationBuilder.class).serverMode(true) {code} But the server tests that runs in embedded mode (when starting the server directly via HotRodServer class) do not apply this setting. > Embedded server tests not using PrivateGlobalConfiguration serverMode > --------------------------------------------------------------------- > > Key: ISPN-8243 > URL: https://issues.jboss.org/browse/ISPN-8243 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query, Test Suite - Server > Affects Versions: 9.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > When starting the infinispan server as a separate process, the following setting is applied to the cache manager: > {code:java} > GlobalConfigurationBuilder builder = ... > builder.addModule(PrivateGlobalConfigurationBuilder.class).serverMode(true) > {code} > But the server tests that run in embedded mode (when starting the server directly via HotRodServer class) do not apply this setting. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8243) Embedded server tests not using PrivateGlobalConfiguration serverMode

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-8243: --------------------------------------- Summary: Embedded server tests not using PrivateGlobalConfiguration serverMode Key: ISPN-8243 URL: https://issues.jboss.org/browse/ISPN-8243 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes When starting the infinispan server as a separate process, the following setting is applied to the cache manager: {code:java} GlobalConfigurationBuilder builder = ... builder.addModule(PrivateGlobalConfigurationBuilder.class).serverMode(true) {code} But the server tests that runs in embedded mode (when starting the server directly via HotRodServer class) do not apply this setting. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8233) Setup Jenkins for building Online images

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8233?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-8233: ------------------------------------------- Quote from Infinispan Internal mailing list: {quote}Hey, I've been talking with Marek Goldmann about the repository and CI for JDG Online Services. It turned out that the Cloud Enablement CI is tied to jboss-container-images [1] organization. It scans repositories and branches and creates jobs based on that (actually, it's pretty clever I must admit). Unfortunately the CE Team is migrating images to Dogen 3. Having this in mind, Marek suggested that we should probably start building new images based on it (here's an example [2]). The biggest concern at this point is the name of the image. Our current JDG 7 image is called "jboss-datagrid-7/datagrid71-openshift" [3]. I'm not sure if this is the naming scheme we'd like to continue. I was thinking about something like this: "jboss-datagrid-services/caching-service". Once we have a name, I can start looking into repository structure. Another obstacle is the way the CI works in the CE Team. They execute Behave tests and validate container itself. After all images are built, they trigger Arquillian Cube tests, which are responsible for checking templates etc. Again, I don't think this is the right approach. So IMO we should create a small script which would start OpenShift, push the image into the local registry and run Arquillian Cube tests against it. The advantage of this approach is that we could run those tests on all machines using well known JUnit framework. The drawback is that this approach is not standard for CE - this is something that only our image will have. Given all that, my plan is the following: I'll start implementing JDG Caching Service in my own repository. This will buy us some time for discussion and I won't be blocked with my work. Once I have something that works, I will adjust it to CE requirements and migrate it to jboss-container-images organization. I will create scripts (probably based on Makefile or Bash) which should be invoked by CI. Later on we can use some JUnit reporting plugin but checking script's exit code will give us enough information - green or not. The new Caching Service will be based on our OpenShift image [3]. This way I won't duplicate Jolokia integration, KUBE_PING module installation etc. The main difference is that we will bootstrap the image using new bootstrap script. For configuration management I plan to use CLI in offline mode. Based on provided configuration, the CLI will adjust cloud.xml file (remove unnecessary caches, endpoints and so on). Please let me know if you have any questions or comments. Thanks, Sebastian [1] https://github.com/jboss-container-images [2] https://github.com/dbecvarik/jboss-amq-6-openshift-image/tree/dogen3 [3] https://github.com/jboss-container-images/jboss-datagrid-7-openshift-imag... > Setup Jenkins for building Online images > ---------------------------------------- > > Key: ISPN-8233 > URL: https://issues.jboss.org/browse/ISPN-8233 > Project: Infinispan > Issue Type: Task > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7968) Investigate how to manage configuration using OpenShift UI

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7968?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7968: -------------------------------------- Status: Open (was: New) > Investigate how to manage configuration using OpenShift UI > ---------------------------------------------------------- > > Key: ISPN-7968 > URL: https://issues.jboss.org/browse/ISPN-7968 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > Infinispan docker image supports [S2I|https://github.com/jboss-dockerfiles/infinispan/tree/master/server/.s...]. We need to figure a way to supply custom configuration using OpenShift UI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8233) Setup Jenkins for building Online images

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8233?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8233: -------------------------------------- Status: Open (was: New) > Setup Jenkins for building Online images > ---------------------------------------- > > Key: ISPN-8233 > URL: https://issues.jboss.org/browse/ISPN-8233 > Project: Infinispan > Issue Type: Task > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8209) Create necessary repositories and branches

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8209?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8209: -------------------------------------- Status: Open (was: New) > Create necessary repositories and branches > ------------------------------------------ > > Key: ISPN-8209 > URL: https://issues.jboss.org/browse/ISPN-8209 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > We need to know what infrastructure we can use to build Online images. Shall we use internal CE infrastructure? What about repositories? -- 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 August 2017