June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9242) Address refactorings brought up in segmented data container review

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9242?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9242: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6065 > Address refactorings brought up in segmented data container review > ------------------------------------------------------------------ > > Key: ISPN-9242 > URL: https://issues.jboss.org/browse/ISPN-9242 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.3.0.CR1 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Final > > > There were some concerns brought up with trying to reduce the # of casts and checking for an UNKNOWN segment. We should be able to refactor these, but it will take a bit more effort, so this has been broken out of that PR. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9142) PreferConsistencyStrategy does not initiate CR when previously independent nodes merge

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9142?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9142: ------------------------------- Status: Open (was: New) > PreferConsistencyStrategy does not initiate CR when previously independent nodes merge > -------------------------------------------------------------------------------------- > > Key: ISPN-9142 > URL: https://issues.jboss.org/browse/ISPN-9142 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > > Two nodes start operating independently and don't know about each other due to a network issue. Both nodes put one record with same key but different value. When the network recovers, CR is not initiated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9142) PreferConsistencyStrategy does not initiate CR when previously independent nodes merge

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9142?page=com.atlassian.jira.plugin.... ] Work on ISPN-9142 started by Ryan Emerson. ------------------------------------------ > PreferConsistencyStrategy does not initiate CR when previously independent nodes merge > -------------------------------------------------------------------------------------- > > Key: ISPN-9142 > URL: https://issues.jboss.org/browse/ISPN-9142 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > > Two nodes start operating independently and don't know about each other due to a network issue. Both nodes put one record with same key but different value. When the network recovers, CR is not initiated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8976) 2 subclusters failed to merge to 1 cluster - IllegalLifecycleStateException

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8976?page=com.atlassian.jira.plugin.... ] Work on ISPN-8976 started by Ryan Emerson. ------------------------------------------ > 2 subclusters failed to merge to 1 cluster - IllegalLifecycleStateException > --------------------------------------------------------------------------- > > Key: ISPN-8976 > URL: https://issues.jboss.org/browse/ISPN-8976 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.4.Final > Reporter: Robert Cernak > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > Attachments: logs.zip > > > At the beginning I have main cluster consisted of 8 nodes. > Then I disconnected main switch on which these nodes were connected. > This leaded to separating main cluster to 2 subclusters - first with 2 nodes and second with 6 nodes. This was expected. > After that I rebooted the nodes. After reboot, nodes again correctly formed 2 subclusters with 2 and 6 members. > After a long time when all nodes were stable with low cpu load, I connected the main switch back which should lead to recreation of main cluster with 8 controllers. > However main cluster did not recovered: > subcluster2 did not change - still had 6 nodes connected - no new members > subcluster1 - nodes did not connect with subcluster2 and after cca 30min they left the cluster. > When I checked infinispan logs of node1 from 1st subcluster I had IllegalLifecycleStateException for every created cache (see included logs.zip): > [transport-thread-744a974a-2811-4f79-ac63-f32daf005d7f-p4-t6] (ClusterCacheStatus.java:599) - ISPN000228: Failed to recover cache XXX state after the current node became the coordinator > org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and cannot be reused. Recreate the cache container. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (HRJS-56) CI for Node.js client

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-56?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-56: --------------------------------- Status: Open (was: New) > CI for Node.js client > --------------------- > > Key: HRJS-56 > URL: https://issues.jboss.org/browse/HRJS-56 > Project: Infinispan Javascript client > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > > Create a Jenkinsfile and accompanying task on ci.infinispan.org so that we can test PRs. > Currently the testsuite requires a server installed in /opt/infinispan-server. It should instead use the maven dependency plugin to download the server from maven locally: > {{mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:copy -DrepoUrl=https://repository.jboss.org/nexus/content/groups/public-jboss/ -Dartifact=org.infinispan.server:infinispan-server-build:9.3.0.Alpha1:zip -Dmdep.stripVersion=true}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (HRJS-56) CI for Node.js client

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-56?page=com.atlassian.jira.plugin.sy... ] Work on HRJS-56 started by Galder Zamarreño. -------------------------------------------- > CI for Node.js client > --------------------- > > Key: HRJS-56 > URL: https://issues.jboss.org/browse/HRJS-56 > Project: Infinispan Javascript client > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > > Create a Jenkinsfile and accompanying task on ci.infinispan.org so that we can test PRs. > Currently the testsuite requires a server installed in /opt/infinispan-server. It should instead use the maven dependency plugin to download the server from maven locally: > {{mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:copy -DrepoUrl=https://repository.jboss.org/nexus/content/groups/public-jboss/ -Dartifact=org.infinispan.server:infinispan-server-build:9.3.0.Alpha1:zip -Dmdep.stripVersion=true}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9294) It is not possible override enable_diagnostics

by Diego Lovison (JIRA)

Diego Lovison created ISPN-9294: ----------------------------------- Summary: It is not possible override enable_diagnostics Key: ISPN-9294 URL: https://issues.jboss.org/browse/ISPN-9294 Project: Infinispan Issue Type: Bug Reporter: Diego Lovison Attachments: pasted_image.png I would like to set enable_diagnostics=true but the following configuration is not working. Edit standalone/configuration/clustered.xml file adding the new property {code:xml} <transport type="UDP" socket-binding="jgroups-udp"> <property name="enable_diagnostics">true</property> </transport> {code} Start the server ./standalone.sh -c clustered.xml Open jcm and check the property. It is still false. See the attachment. The desirable solution could be a change in the following files to: - default-configs/default-jgroups-udp.xml - default-configs/default-jgroups-tcp.xml {noformat} enable_diagnostics="${jgroups.udp.enable_diagnostics:false}" {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9190) Make trace logging faster by writing a separate log file for each test

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9190?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9190: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make trace logging faster by writing a separate log file for each test > ---------------------------------------------------------------------- > > Key: ISPN-9190 > URL: https://issues.jboss.org/browse/ISPN-9190 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Final > > > Logging each test to a separate file is cheaper because each test uses a separate appender, so there's no contention. The total size may also be smaller (with {{CompressedFileAppender}}) because the test name is repeated a lot and there isn't so much overlap between different tests. > Most important, keeping only the logs of failed tests becomes much faster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8944) Maven profile traceTests no longer works

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8944?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8944: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Maven profile traceTests no longer works > ---------------------------------------- > > Key: ISPN-8944 > URL: https://issues.jboss.org/browse/ISPN-8944 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.2.0.Final > Reporter: William Burns > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > > When trying to run -PtraceTests for maven the tests print out this warning > ERROR StatusLogger File not found in file system or classpath: log4j2-trace.xml > We currently just pass log4j2-trace.xml. Unfortunately this file is no longer in the classpath and no module has that file relative to its directory. We need to add something for root-dir profiles it seems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9282) Near-Real-Time indexes lost when server is stopped

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9282?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9282: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.6.Final 9.3.0.Final Resolution: Done > Near-Real-Time indexes lost when server is stopped > -------------------------------------------------- > > Key: ISPN-9282 > URL: https://issues.jboss.org/browse/ISPN-9282 > Project: Infinispan > Issue Type: Bug > Components: Indexing, Server > Affects Versions: 9.3.0.CR1, 9.2.5.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.2.6.Final, 9.3.0.Final > > > The server does not respect the stop order of the caches dictated by cache manager and tries to stop all caches in random order. > When a cache is indexed and uses the "near-real-time" index manager, it relies on the indexing caches being available during shutdown of the data cache so that it can properly flush the index to persistence storage, and this fails due to one or more index caches being unavailable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 June 2018