March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7553) Replicated cache with numOwners=1 doesn't send writes to backups

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7553: ---------------------------------- Summary: Replicated cache with numOwners=1 doesn't send writes to backups Key: ISPN-7553 URL: https://issues.jboss.org/browse/ISPN-7553 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.0.0.CR2 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Critical Fix For: 9.0.0.Final {{BaseDistributionInterceptor.primaryReturnHandler()}} doesn't replicate writes to the backups if {{cacheConfiguration.clustering().hash().numOwners() == 1}}. That check is incorrect, because a segment can have more owners than configured: 1. In a replicated cache, the configured {{numOwners}} is ignored, and all the members are owners. 1. Even in a distributed cache, during rebalance, the segments being moved will have more than {{numOwners}} owners. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7544) Administration console - server cards do not indicate correct status in some cases

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7544?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7544. -------------------------------- Fix Version/s: 9.0.0.Final Assignee: Vladimir Blagojevic Resolution: Done > Administration console - server cards do not indicate correct status in some cases > ---------------------------------------------------------------------------------- > > Key: ISPN-7544 > URL: https://issues.jboss.org/browse/ISPN-7544 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Final > > > Server cards (clusters tab -> cluster) don't indicate that the server is in reload-required, restart required state. - they show green check icon in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7469) Administration console - JDBC store elements have the same IDs

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7469?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7469: ------------------------------- Summary: Administration console - JDBC store elements have the same IDs (was: Administration console - some elements have the same IDs) > Administration console - JDBC store elements have the same IDs > -------------------------------------------------------------- > > Key: ISPN-7469 > URL: https://issues.jboss.org/browse/ISPN-7469 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR1 > Reporter: Roman Macor > Assignee: Ryan Emerson > > Some elements have the same IDs. > Steps to reproduce: > Click on cache container -> cache -> configuration -> store -> select String keyed JDBC store -> click on String keyed table -> several input elements have the same ID -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7552) Rolling Upgrade enhancements

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7552?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7552: ------------------------------------ Description: The rolling upgrade can migrate data between clusters with no downtime, but currently the procedure is somehow complicated. Some proposals to improve it: * Provide scripts to automate the procedure * Provide pre-canned configurations to start the new cluster or scripts to automate the remote cache store addition * Server initiated cluster switch: the server would send a new topology to clients so that manual shutdown, change config and startup is not necessary Others? was: The rolling upgrade can migrate data between clusters with no downtime, but currently the procedure is somehow complicated. Some proposals to improve it: * Provide scripts to automate the procedure * Provide pre-canned configurations to start the new cluster * Server initiated cluster switch: the server would send a new topology to clients so that manual shutdown, change config and startup is not necessary Others? > Rolling Upgrade enhancements > ---------------------------- > > Key: ISPN-7552 > URL: https://issues.jboss.org/browse/ISPN-7552 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Gustavo Fernandes > > The rolling upgrade can migrate data between clusters with no downtime, but currently the procedure is somehow complicated. > Some proposals to improve it: > * Provide scripts to automate the procedure > * Provide pre-canned configurations to start the new cluster or scripts to automate the remote cache store addition > * Server initiated cluster switch: the server would send a new topology to clients so that manual shutdown, change config and startup is not necessary > Others? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7469) Administration console - JDBC store elements have the same IDs

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7469?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7469: ------------------------------- Status: Open (was: New) > Administration console - JDBC store elements have the same IDs > -------------------------------------------------------------- > > Key: ISPN-7469 > URL: https://issues.jboss.org/browse/ISPN-7469 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR1 > Reporter: Roman Macor > Assignee: Ryan Emerson > > Some elements have the same IDs. > Steps to reproduce: > Click on cache container -> cache -> configuration -> store -> select String keyed JDBC store -> click on String keyed table -> several input elements have the same ID -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7469) Administration console - JDBC store elements have the same IDs

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7469?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7469: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/197 > Administration console - JDBC store elements have the same IDs > -------------------------------------------------------------- > > Key: ISPN-7469 > URL: https://issues.jboss.org/browse/ISPN-7469 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR1 > Reporter: Roman Macor > Assignee: Ryan Emerson > > Some elements have the same IDs. > Steps to reproduce: > Click on cache container -> cache -> configuration -> store -> select String keyed JDBC store -> click on String keyed table -> several input elements have the same ID -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7552) Rolling Upgrade enhancements

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7552?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7552: ------------------------------------ Summary: Rolling Upgrade enhancements (was: Rolling Upgrade enhancement) > Rolling Upgrade enhancements > ---------------------------- > > Key: ISPN-7552 > URL: https://issues.jboss.org/browse/ISPN-7552 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Gustavo Fernandes > > The rolling upgrade can migrate data between clusters with no downtime, but currently the procedure is somehow complicated. > Some proposals to improve it: > * Provide scripts to automate the procedure > * Provide pre-canned configurations to start the new cluster > * Server initiated cluster switch: the server would send a new topology to clients so that manual shutdown, change config and startup is not necessary > Others? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7552) Rolling Upgrade enhancement

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-7552: --------------------------------------- Summary: Rolling Upgrade enhancement Key: ISPN-7552 URL: https://issues.jboss.org/browse/ISPN-7552 Project: Infinispan Issue Type: Enhancement Components: Server Reporter: Gustavo Fernandes The rolling upgrade can migrate data between clusters with no downtime, but currently the procedure is somehow complicated. Some proposals to improve it: * Provide scripts to automate the procedure * Provide pre-canned configurations to start the new cluster * Server initiated cluster switch: the server would send a new topology to clients so that manual shutdown, change config and startup is not necessary Others? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7065) Collect clustered memory statistics

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7065?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7065: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4928 > Collect clustered memory statistics > ----------------------------------- > > Key: ISPN-7065 > URL: https://issues.jboss.org/browse/ISPN-7065 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management, Server > Reporter: Tristan Tarrant > Assignee: Ryan Emerson > Fix For: 9.0.0.Final > > > Currently, memory stats (such as used/free heap) in a cluster / domain need to be collected by looking at the JVM memory mbeans for each individual node. > We should provide an MBean which provides aggregated cluster statistics for this as well as exposing this information over the DMR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7551) Use invokeAsync in CacheImpl.*async methods

by Radim Vansa (JIRA)

Radim Vansa created ISPN-7551: --------------------------------- Summary: Use invokeAsync in CacheImpl.*async methods Key: ISPN-7551 URL: https://issues.jboss.org/browse/ISPN-7551 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 9.0.0.CR2 Reporter: Radim Vansa Assignee: Radim Vansa Now that we async internals, we shouldn't block at the CacheImpl level -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017