April 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3018) Implement a REST cache store

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3018: ------------------------------------- Summary: Implement a REST cache store Key: ISPN-3018 URL: https://issues.jboss.org/browse/ISPN-3018 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Blocker Fix For: 5.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2973: -------------------------------- Priority: Major (was: Critical) > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Tristan Tarrant > Fix For: 5.2.6.Final, 5.3.0.Beta1, 5.3.0.Final > > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2973: ------------------------------------- Assignee: Tristan Tarrant (was: Dan Berindei) > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.6.Final, 5.3.0.Beta1, 5.3.0.Final > > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2973: ------------------------------------- ISPN-2577 should solve the root of the problem. Not sure we can back port ISPN-2577 to 5.2 this ([~dan.berindei] ?), so we should amend the retry logic on 5.2. > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.6.Final, 5.3.0.Beta1, 5.3.0.Final > > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2973: -------------------------------- Fix Version/s: 5.2.6.Final 5.3.0.Beta1 5.3.0.Final > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.6.Final, 5.3.0.Beta1, 5.3.0.Final > > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2973: -------------------------------- Assignee: Dan Berindei (was: Tristan Tarrant) > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Dan Berindei > Priority: Critical > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2973: -------------------------------- Priority: Critical (was: Major) > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Tristan Tarrant > Priority: Critical > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3017) Add tests for queries with FSDirectory

by Martin Gencur (JIRA)

Martin Gencur created ISPN-3017: ----------------------------------- Summary: Add tests for queries with FSDirectory Key: ISPN-3017 URL: https://issues.jboss.org/browse/ISPN-3017 Project: Infinispan Issue Type: Task Components: Lucene Directory Affects Versions: 5.3.0.Alpha1 Reporter: Martin Gencur Assignee: Martin Gencur Fix For: 5.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2713) REBALANCE_START and REBALANCE_CONFIRM commands deadlock when RSVP.ack_on_delivery=true

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2713?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-2713. -------------------------------- Fix Version/s: 5.3.0.Beta1 Resolution: Done The ISPN-2825 fix eliminated the deadlock. > REBALANCE_START and REBALANCE_CONFIRM commands deadlock when RSVP.ack_on_delivery=true > -------------------------------------------------------------------------------------- > > Key: ISPN-2713 > URL: https://issues.jboss.org/browse/ISPN-2713 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 5.3.0.Beta1, 5.3.0.Final > > > When the coordinator sends a REBALANCE_START command, it holds a lock on the ClusterCacheStatus until it receives the responses from all the other members. > If a node doesn't need to request any new state, it sends the rebalance confirmation to the coordinator on the same thread that received the REBALANCE_START command. The REBALANCE_CONFIRM command also wants to acquire a lock on the ClusterCacheStatus on the coordinator, but because the REBALANCE_CONFIRM command is sent asynchronously, it doesn't deadlock with the thread waiting for REBALANCE_START responses on the coordinator. > At least, that's what happens when {{RSVP.ack_on_delivery=false}} (the Infinispan default). When {{RSVP.ack_on_delivery=true}} (the JGroups default), the "asynchronous" REBALANCE_CONFIRM command becomes synchronous, and it generates a deadlock. The rebalance then fails after the RSVP timeout expires (10 seconds by default). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-777) Race conditions in cleaning up stale locks held by dead members in a cluster

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-777?page=com.atlassian.jira.plugin.s... ] Mircea Markus resolved ISPN-777. -------------------------------- Resolution: Out of Date should be fixed in 5.2. > Race conditions in cleaning up stale locks held by dead members in a cluster > ---------------------------------------------------------------------------- > > Key: ISPN-777 > URL: https://issues.jboss.org/browse/ISPN-777 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency > Affects Versions: 4.2.0.BETA1 > Reporter: Vladimir Blagojevic > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.3.0.Final > > Attachments: CacheScheduledCounter.java, ISPN-777_output.txt > > > It seems that rollback sometimes does not release acquired eager locks. See attached test program and run two JVM instances on the same machine. Program schedules a task to run every 5 seconds. Tasks simply locks a key, gets the value, increases the value and puts it back surrounded by begin/commit/rollback tx boundary. > Steps to reproduce (keep repeating steps until problem is encountered): > 1) Kill one running instance. > 2) Restart it > See attached example output of a run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2013