March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7590) Invocation idempotence

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7590?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7590: ------------------------------ Fix Version/s: 9.3.0.Final > Invocation idempotence > ---------------------- > > Key: ISPN-7590 > URL: https://issues.jboss.org/browse/ISPN-7590 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Radim Vansa > Assignee: Radim Vansa > Labels: consistency > Fix For: 9.3.0.Final > > > This is an umbrella JIRA to change the way how we deal with retries after topology change. > Please link any outstanding issues that refer to incorrect return values of command during topology change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7590) Invocation idempotence

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7590?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7590: ------------------------------ Summary: Invocation idempotence (was: Entry version history) > Invocation idempotence > ---------------------- > > Key: ISPN-7590 > URL: https://issues.jboss.org/browse/ISPN-7590 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Radim Vansa > Assignee: Radim Vansa > Labels: consistency > > This is an umbrella JIRA to change the way how we deal with retries after topology change. > Please link any outstanding issues that refer to incorrect return values of command during topology change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8921) KeyStream stream operations use entrySet on remote nodes

by William Burns (JIRA)

William Burns created ISPN-8921: ----------------------------------- Summary: KeyStream stream operations use entrySet on remote nodes Key: ISPN-8921 URL: https://issues.jboss.org/browse/ISPN-8921 Project: Infinispan Issue Type: Bug Components: Streams Affects Versions: 9.2.0.Final Reporter: William Burns Assignee: William Burns Fix For: 9.3.0.Final Currently when a remote stream operation is performed it is always done using an entrySet. This causes a lot of overhead for keySet operations - especially if there is a store! We should support key based streams for remote nodes in addition to entry set. There is nothing stopping this currently, all we should need is an additional argument for StreamIteratorRequestCommand to say if it is keyset or entry set. Then the LocalStreamManaterImpl and IteratorHandler need very minor tweaks. This should help operations such as size when using a store quite a bit depending on the store implementation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8916) Enable cross origin requests for the admin console

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8916?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8916: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5823 > Enable cross origin requests for the admin console > -------------------------------------------------- > > Key: ISPN-8916 > URL: https://issues.jboss.org/browse/ISPN-8916 > Project: Infinispan > Issue Type: Sub-task > Reporter: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8916) Enable cross origin requests for the admin console

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8916?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-8916: --------------------------------------- Assignee: Gustavo Fernandes > Enable cross origin requests for the admin console > -------------------------------------------------- > > Key: ISPN-8916 > URL: https://issues.jboss.org/browse/ISPN-8916 > Project: Infinispan > Issue Type: Sub-task > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8916) Enable cross origin requests for the admin console

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8916?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8916: ------------------------------------ Status: Open (was: New) > Enable cross origin requests for the admin console > -------------------------------------------------- > > Key: ISPN-8916 > URL: https://issues.jboss.org/browse/ISPN-8916 > Project: Infinispan > Issue Type: Sub-task > Reporter: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8902) Client hangs forever when IP address not accessible

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8902?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-8902: ---------------------------------------- Added trace logs > Client hangs forever when IP address not accessible > --------------------------------------------------- > > Key: ISPN-8902 > URL: https://issues.jboss.org/browse/ISPN-8902 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.2.0.Final > Reporter: Galder Zamarreño > Assignee: Radim Vansa > Fix For: 9.2.1.Final > > Attachments: infinispan.log > > > Can be replicated with code [here|https://github.com/galderz/jdg-sandbox/blob/master/client/src/main/j...] > Thread dump is [here|https://gist.github.com/galderz/89b387b9e8b644456c18653e7b3c3c38]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8902) Client hangs forever when IP address not accessible

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8902?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8902: ----------------------------------- Attachment: infinispan.log > Client hangs forever when IP address not accessible > --------------------------------------------------- > > Key: ISPN-8902 > URL: https://issues.jboss.org/browse/ISPN-8902 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.2.0.Final > Reporter: Galder Zamarreño > Assignee: Radim Vansa > Fix For: 9.2.1.Final > > Attachments: infinispan.log > > > Can be replicated with code [here|https://github.com/galderz/jdg-sandbox/blob/master/client/src/main/j...] > Thread dump is [here|https://gist.github.com/galderz/89b387b9e8b644456c18653e7b3c3c38]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8860) Lazy start counter's caches

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8860?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8860: ------------------------------ Status: Open (was: New) > Lazy start counter's caches > --------------------------- > > Key: ISPN-8860 > URL: https://issues.jboss.org/browse/ISPN-8860 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Counter > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Goal: if counter's are used, there is no need to start counter's caches! > Main change: > * remove {{__counter_configuration}} and use the {{state-cache}} to store counter's configuration > Summary: > * When the first counter is defined and stored in the {{state-cache}}, the {{__counter}} cache is started. > * When a node joins, it starts the {{__counter}} cache if it finds a counter's configured stored > * We need to persist the counter's configuration (for persisted counters only!) manually since the {{state-cache}} isn't persisted > Issues > * the {{state-cache}} is available during partitions! same counter can be defined with different configuration :( > users have to deal with it while I can't find a way to resolve a conflict. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8860) Lazy start counter's caches

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8860?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8860: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5822 > Lazy start counter's caches > --------------------------- > > Key: ISPN-8860 > URL: https://issues.jboss.org/browse/ISPN-8860 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Counter > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Goal: if counter's are used, there is no need to start counter's caches! > Main change: > * remove {{__counter_configuration}} and use the {{state-cache}} to store counter's configuration > Summary: > * When the first counter is defined and stored in the {{state-cache}}, the {{__counter}} cache is started. > * When a node joins, it starts the {{__counter}} cache if it finds a counter's configured stored > * We need to persist the counter's configuration (for persisted counters only!) manually since the {{state-cache}} isn't persisted > Issues > * the {{state-cache}} is available during partitions! same counter can be defined with different configuration :( > users have to deal with it while I can't find a way to resolve a conflict. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 March 2018