April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11606) SB Starter Doc Attributes

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11606?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11606: -------------------------------- Status: Open (was: New) > SB Starter Doc Attributes > ------------------------- > > Key: ISPN-11606 > URL: https://issues.redhat.com/browse/ISPN-11606 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > > Update attributes for SB starter docs. Versions should be in the product-versions.adoc file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11583) Cannot change to udp jgroups protocol in server test suite

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11583?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11583: ------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cannot change to udp jgroups protocol in server test suite > ---------------------------------------------------------- > > Key: ISPN-11583 > URL: https://issues.redhat.com/browse/ISPN-11583 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 11.0.0.Dev04, 10.1.6.Final > > > When running {{mvn verify -Dit.test=HotRodCacheQueries -Dinfinispan.test.jgroups.protocol=udp -pl server/tests}} it won't be able to change to UDP because {{ClusteredServerTest.xml}} has a static value for > {noformat} > <xi:include href="jgroups/tcp.xml"/> > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11583) Cannot change to udp jgroups protocol in server test suite

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11583?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11583: ------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8152, https://github.com/infinispan/infinispan/pull/8175 (was: https://github.com/infinispan/infinispan/pull/8152) > Cannot change to udp jgroups protocol in server test suite > ---------------------------------------------------------- > > Key: ISPN-11583 > URL: https://issues.redhat.com/browse/ISPN-11583 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 11.0.0.Dev04, 10.1.6.Final > > > When running {{mvn verify -Dit.test=HotRodCacheQueries -Dinfinispan.test.jgroups.protocol=udp -pl server/tests}} it won't be able to change to UDP because {{ClusteredServerTest.xml}} has a static value for > {noformat} > <xi:include href="jgroups/tcp.xml"/> > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11619) Remove deprecated RemoteCache#getVersioned

by Will Burns (Jira)

Will Burns created ISPN-11619: --------------------------------- Summary: Remove deprecated RemoteCache#getVersioned Key: ISPN-11619 URL: https://issues.redhat.com/browse/ISPN-11619 Project: Infinispan Issue Type: Task Components: Hot Rod Reporter: Will Burns Assignee: Will Burns Fix For: 11.0.0.Dev04 The getVersioned method has been deprecated since 9.0.0.Alpha0. We should finally kill it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11617) Remove org.infinispan.metadata.InternalMetadata

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11617?page=com.atlassian.jira.plugi... ] Ryan Emerson reassigned ISPN-11617: ----------------------------------- Assignee: (was: Ryan Emerson) > Remove org.infinispan.metadata.InternalMetadata > ----------------------------------------------- > > Key: ISPN-11617 > URL: https://issues.redhat.com/browse/ISPN-11617 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 11.0.0.Dev03 > Reporter: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Dev04 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11618) CacheWriter#bulkUpdate return value is ignored in many places

by Will Burns (Jira)

Will Burns created ISPN-11618: --------------------------------- Summary: CacheWriter#bulkUpdate return value is ignored in many places Key: ISPN-11618 URL: https://issues.redhat.com/browse/ISPN-11618 Project: Infinispan Issue Type: Bug Components: Core, Loaders and Stores Reporter: Will Burns We added a non blocking SPI for CacheWriter bulk operation. Unfortunately all callers of this were not changed to handle this in a non blocking fashion. This has gone largely unchecked due to the actual implementations being blocking. We should fix these references so they will work as these stores become non blocking. Example locations: https://github.com/infinispan/infinispan/blob/8cf2e67f190aca109478fbeba6d... https://github.com/infinispan/infinispan/blob/7d8a18d3425e614ff5e0ebcf421... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11601) Remove KeyFilter

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11601?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-11601. --------------------------------- Fix Version/s: 11.0.0.Dev04 Resolution: Done > Remove KeyFilter > ---------------- > > Key: ISPN-11601 > URL: https://issues.redhat.com/browse/ISPN-11601 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Dev04 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11617) Remove org.infinispan.metadata.InternalMetadata

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-11617: ----------------------------------- Summary: Remove org.infinispan.metadata.InternalMetadata Key: ISPN-11617 URL: https://issues.redhat.com/browse/ISPN-11617 Project: Infinispan Issue Type: Sub-task Components: Core Affects Versions: 11.0.0.Dev03 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 11.0.0.Dev04 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-138) Log a warning when the write-behind modification queue is full

by Ryan Emerson (Jira)

Ryan Emerson created IPROTO-138: ----------------------------------- Summary: Log a warning when the write-behind modification queue is full Key: IPROTO-138 URL: https://issues.redhat.com/browse/IPROTO-138 Project: Infinispan ProtoStream Issue Type: Enhancement Reporter: Ryan Emerson When the async-modification-queue becomes full, writes are performed synchronously. Currently it's not possible from the logs to ascertain that this has happened, even though it could have a significant impact on performance. We should log when the queue is full, followed by a follow up message saying how many writes we written synchronously once it's no longer full. This will provide the user with feedback that can be used to more accurately configured the queue size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11616) Log a warning when the write-behind modification queue is full

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11616?page=com.atlassian.jira.plugi... ] Ryan Emerson moved IPROTO-138 to ISPN-11616: -------------------------------------------- Project: Infinispan (was: Infinispan ProtoStream) Key: ISPN-11616 (was: IPROTO-138) > Log a warning when the write-behind modification queue is full > -------------------------------------------------------------- > > Key: ISPN-11616 > URL: https://issues.redhat.com/browse/ISPN-11616 > Project: Infinispan > Issue Type: Enhancement > Reporter: Ryan Emerson > Priority: Major > > When the async-modification-queue becomes full, writes are performed synchronously. Currently it's not possible from the logs to ascertain that this has happened, even though it could have a significant impact on performance. We should log when the queue is full, followed by a follow up message saying how many writes we written synchronously once it's no longer full. This will provide the user with feedback that can be used to more accurately configured the queue size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2020