January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11189) Modules query and query-core have overlapping logging id ranges

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11189?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11189: --------------------------------- Sprint: DataGrid Sprint #39 > Modules query and query-core have overlapping logging id ranges > --------------------------------------------------------------- > > Key: ISPN-11189 > URL: https://issues.redhat.com/browse/ISPN-11189 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11189) Modules query and query-core have overlapping logging id ranges

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11189?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11189: --------------------------------- Status: Open (was: New) > Modules query and query-core have overlapping logging id ranges > --------------------------------------------------------------- > > Key: ISPN-11189 > URL: https://issues.redhat.com/browse/ISPN-11189 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11189) Modules query and query-core have overlapping logging id ranges

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-11189: ------------------------------------ Summary: Modules query and query-core have overlapping logging id ranges Key: ISPN-11189 URL: https://issues.redhat.com/browse/ISPN-11189 Project: Infinispan Issue Type: Bug Components: Embedded Querying Affects Versions: 10.1.0.Final Reporter: Nistor Adrian Assignee: Nistor Adrian Fix For: 10.1.2.Final, 11.0.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11188) Deprecate ClientEvents.mkCachefailoverEvent

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11188?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11188: --------------------------------- Status: Open (was: New) > Deprecate ClientEvents.mkCachefailoverEvent > ------------------------------------------- > > Key: ISPN-11188 > URL: https://issues.redhat.com/browse/ISPN-11188 > Project: Infinispan > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.2.Final > > > This should have been an internal method. There is nothing a client can do with this except maybe check than an even is a failover event by doing an == comparison. But that's not really how it should be done since we have an even type enum that better serves that purpose. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11188) Deprecate ClientEvents.mkCachefailoverEvent

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11188?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11188: --------------------------------- Description: This should have been an internal method. There is nothing a client can do with this except maybe check than an even is a failover event by doing an == comparison. But that's not really how it should be done since we have an even type enum that better serves that purpose. This can be removed in 11. was:This should have been an internal method. There is nothing a client can do with this except maybe check than an even is a failover event by doing an == comparison. But that's not really how it should be done since we have an even type enum that better serves that purpose. > Deprecate ClientEvents.mkCachefailoverEvent > ------------------------------------------- > > Key: ISPN-11188 > URL: https://issues.redhat.com/browse/ISPN-11188 > Project: Infinispan > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.2.Final > > > This should have been an internal method. There is nothing a client can do with this except maybe check than an even is a failover event by doing an == comparison. But that's not really how it should be done since we have an even type enum that better serves that purpose. > This can be removed in 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11188) Deprecate ClientEvents.mkCachefailoverEvent

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-11188: ------------------------------------ Summary: Deprecate ClientEvents.mkCachefailoverEvent Key: ISPN-11188 URL: https://issues.redhat.com/browse/ISPN-11188 Project: Infinispan Issue Type: Task Reporter: Nistor Adrian Assignee: Nistor Adrian Fix For: 10.1.2.Final This should have been an internal method. There is nothing a client can do with this except maybe check than an even is a failover event by doing an == comparison. But that's not really how it should be done since we have an even type enum that better serves that purpose. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11187) Completely remove support for Index.LOCAL in parser and config

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-11187: ------------------------------------ Summary: Completely remove support for Index.LOCAL in parser and config Key: ISPN-11187 URL: https://issues.redhat.com/browse/ISPN-11187 Project: Infinispan Issue Type: Task Reporter: Nistor Adrian Assignee: Nistor Adrian Fix For: 11.0.0.Final Support for Index.LOCAL has been removed already but in some places in code we still accept it leniently and convert it to Index.PRIMARY_OWNER and issue a warning in 10.x to ease config migration. In 11 we should completely remove that also. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11187) Completely remove support for Index.LOCAL in parser and config

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11187?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11187: --------------------------------- Status: Open (was: New) > Completely remove support for Index.LOCAL in parser and config > -------------------------------------------------------------- > > Key: ISPN-11187 > URL: https://issues.redhat.com/browse/ISPN-11187 > Project: Infinispan > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Final > > > Support for Index.LOCAL has been removed already but in some places in code we still accept it leniently and convert it to Index.PRIMARY_OWNER and issue a warning in 10.x to ease config migration. In 11 we should completely remove that also. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10957) Index/Query by key

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10957?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-10957: ----------------------------------- Fix Version/s: 11.0.0.Final > Index/Query by key > ------------------ > > Key: ISPN-10957 > URL: https://issues.redhat.com/browse/ISPN-10957 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Tristan Tarrant > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Final > > > We should offer the ability to query by key both in non-indexed mode as well as adding the key to the index using some special field name -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11113) ScatteredDelayedAvailabilityUpdateTest takes too long

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11113?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11113: ----------------------------------- Fix Version/s: 10.1.2.Final (was: 10.1.1.Final) > ScatteredDelayedAvailabilityUpdateTest takes too long > ----------------------------------------------------- > > Key: ISPN-11113 > URL: https://issues.redhat.com/browse/ISPN-11113 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.1.2.Final, 11.0.0.Final > > > Partition handling tests use {{LOCAL_PING.setClusterName()}} with a unique name to disable discovery, otherwise partitions would try to merge while they are supposed to stay separate. > But {{LOCAL_PING}} uses the cluster name on stop to remove the node from the static discovery map. If the test doesn't change the cluster name back, {{LOCAL_PING}} doesn't remove the node, the next test method sees an existing coordinator, and tries to connect to it. When a test has lots of test methods, like {{ScatteredDelayedAvailabilityUpdateTest}}, each test method leaves one more coordinator in the discovery map, and each test method takes longer to start the first method. > {noformat} > 09:08:52,758 DEBUG (testng:[]) [GMS] address=NodeA-30899, cluster=org.infinispan.partitionhandling.ScatteredDelayedAvailabilityUpdateTest[SCATTERED_SYNC, bias=NEVER, DENY_READ_WRITES], physical address=127.0.0.1:51941 > 09:08:52,774 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:08:54,774 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 0 > 09:08:54,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-64297 > 09:08:56,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-64297 timed out (after 2000 ms), on try 0 > 09:08:56,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-48475 > 09:08:58,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-48475 timed out (after 2000 ms), on try 0 > 09:08:58,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-17288 > 09:09:00,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-17288 timed out (after 2000 ms), on try 0 > 09:09:00,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:02,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 0 > 09:09:02,776 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:09:04,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 1 > ... > 09:09:12,777 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:14,778 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 2 > ... > 09:09:22,780 WARN (testng:[]) [GMS] NodeA-30899: too many JOIN attempts (3): becoming singleton > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020