March 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2639) Write an adaptor for the JSR 107 API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2639?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2639: -------------------------------- Fix Version/s: 5.3.0.Alpha1 > Write an adaptor for the JSR 107 API > ------------------------------------ > > Key: ISPN-2639 > URL: https://issues.jboss.org/browse/ISPN-2639 > Project: Infinispan > Issue Type: Feature Request > Components: JCache > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > This should be a new Infinispan maven module, implement the API and pass the TCK suite as defined here: https://github.com/jsr107 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2639) Write an adaptor for the JSR 107 API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2639?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2639: -------------------------------- Priority: Blocker (was: Major) > Write an adaptor for the JSR 107 API > ------------------------------------ > > Key: ISPN-2639 > URL: https://issues.jboss.org/browse/ISPN-2639 > Project: Infinispan > Issue Type: Feature Request > Components: JCache > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > This should be a new Infinispan maven module, implement the API and pass the TCK suite as defined here: https://github.com/jsr107 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2636) Support for Total Order Broadcast(TOB) Transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2636?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2636: -------------------------------- Fix Version/s: 5.3.0.Alpha1 > Support for Total Order Broadcast(TOB) Transactions > --------------------------------------------------- > > Key: ISPN-2636 > URL: https://issues.jboss.org/browse/ISPN-2636 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > The Total Order based commit protocol is a multi-master scheme as currently Two Phase Commit implementation. > This protocol relies on the concept of totally ordered delivery of messages which, informally, implies that each node which delivers a set of messages M, delivers them in the same order. > This protocol comes with two advantages. > 1) transactions can be committed in one phase, as they are delivered in the same order by the nodes that receive them. > 2) it totally avoids deadlocks. > The weakness point of this protocol is the fact that its implementation relies on a single thread per node which validates and commit transactions. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2402) Cache operations or transactions should never fail with SuspectException

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2402?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2402: -------------------------------- Fix Version/s: 5.3.0.Beta1 (was: 5.3.0.Alpha1) > Cache operations or transactions should never fail with SuspectException > ------------------------------------------------------------------------ > > Key: ISPN-2402 > URL: https://issues.jboss.org/browse/ISPN-2402 > Project: Infinispan > Issue Type: Task > Components: RPC, State transfer > Affects Versions: 5.2.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 5.3.0.Beta1 > > Attachments: vrstt.log > > > This is an extension of ISPN-1896 of sorts, but for all the cache operations that are visible to the user. > After a node leaves, the other nodes that have sent commands to that node should either ignore SuspectExceptions or, if not possible, they should retry the operation (e.g. if they didn't get any response back). > For example, VersionReplStateTransferTest quite often on my machine with a SuspectException, because the versioned prepare command expects a response from the coordinator and the coordinator has just left. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2635) Support for Total Order Multicast Transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2635?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2635: -------------------------------- Fix Version/s: 5.3.0.Alpha1 > Support for Total Order Multicast Transactions > ---------------------------------------------- > > Key: ISPN-2635 > URL: https://issues.jboss.org/browse/ISPN-2635 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > Based on CloudTM's implementation. > The Total Order based commit protocol is a multi-master scheme as currently Two Phase Commit implementation. > This protocol relies on the concept of totally ordered delivery of messages which, informally, implies that each node which delivers a set of messages M, delivers them in the same order. > This protocol comes with two advantages. > 1) transactions can be committed in one phase, as they are delivered in the same order by the nodes that receive them. > 2) it totally avoids deadlocks. > The weakness point of this protocol is the fact that its implementation relies on a single thread per node which validates and commit transactions. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2635) Support for Total Order Multicast Transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2635?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2635: -------------------------------- Priority: Blocker (was: Major) > Support for Total Order Multicast Transactions > ---------------------------------------------- > > Key: ISPN-2635 > URL: https://issues.jboss.org/browse/ISPN-2635 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Priority: Blocker > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > Based on CloudTM's implementation. > The Total Order based commit protocol is a multi-master scheme as currently Two Phase Commit implementation. > This protocol relies on the concept of totally ordered delivery of messages which, informally, implies that each node which delivers a set of messages M, delivers them in the same order. > This protocol comes with two advantages. > 1) transactions can be committed in one phase, as they are delivered in the same order by the nodes that receive them. > 2) it totally avoids deadlocks. > The weakness point of this protocol is the fact that its implementation relies on a single thread per node which validates and commit transactions. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2835) Issues w/ M/R test cases if cache are not explicitly started on all nodes

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2835?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2835: -------------------------------- Fix Version/s: (was: 5.3.0.Alpha1) > Issues w/ M/R test cases if cache are not explicitly started on all nodes > ------------------------------------------------------------------------- > > Key: ISPN-2835 > URL: https://issues.jboss.org/browse/ISPN-2835 > Project: Infinispan > Issue Type: Feature Request > Components: Core API, Distributed Execution and Map/Reduce > Reporter: Ray Tsang > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > Attachments: mr-test-src.zip > > > I ran into some issues while using M/R. The gist of the issue I was seeing is that: > Start a cluster of Embedded Caches, like 4 nodes > Put in 100 elements > Run a simple M/R job to count the number of keys > If I run the M/R job using the node I'm inserting elements into as coordinator - the result is 100 > But if I run the M/R job using a different node as coordinator, the result is less than 100 > More interestingly, I can pause for 5 seconds and run the M/R jobs again, the results are always less than 100 > This behavior doens't occur if I explicitly run cacheManager.getCache() for each of the nodes... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2835) Issues w/ M/R test cases if cache are not explicitly started on all nodes

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2835?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2835: -------------------------------- Fix Version/s: 5.3.0.Alpha1 > Issues w/ M/R test cases if cache are not explicitly started on all nodes > ------------------------------------------------------------------------- > > Key: ISPN-2835 > URL: https://issues.jboss.org/browse/ISPN-2835 > Project: Infinispan > Issue Type: Feature Request > Components: Core API, Distributed Execution and Map/Reduce > Reporter: Ray Tsang > Assignee: Galder Zamarreño > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > Attachments: mr-test-src.zip > > > I ran into some issues while using M/R. The gist of the issue I was seeing is that: > Start a cluster of Embedded Caches, like 4 nodes > Put in 100 elements > Run a simple M/R job to count the number of keys > If I run the M/R job using the node I'm inserting elements into as coordinator - the result is 100 > But if I run the M/R job using a different node as coordinator, the result is less than 100 > More interestingly, I can pause for 5 seconds and run the M/R jobs again, the results are always less than 100 > This behavior doens't occur if I explicitly run cacheManager.getCache() for each of the nodes... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2893) GUI Demo sample configs include old RELAY configuration instead of RELAY2

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2893?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2893: -------------------------------- Fix Version/s: 5.3.0.Final (was: 5.3.0.Alpha1) > GUI Demo sample configs include old RELAY configuration instead of RELAY2 > ------------------------------------------------------------------------- > > Key: ISPN-2893 > URL: https://issues.jboss.org/browse/ISPN-2893 > Project: Infinispan > Issue Type: Feature Request > Components: Demos and Tutorials > Affects Versions: 5.2.3.Final > Reporter: Tristan Tarrant > Assignee: Mircea Markus > Priority: Minor > Fix For: 5.3.0.Final > > > The files in infinispan/demos/gui/src/main/release/etc/config-samples related to xsite configuration still reference the old RELAY stack instead of the newer RELAY2. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2850) CLI Synopsis[info, stats] need to be changed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2850?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2850: ----------------------------------------------- Vitalii Chepeliuk <vchepeli(a)redhat.com> changed the Status of [bug 915268|https://bugzilla.redhat.com/show_bug.cgi?id=915268] from ON_QA to ASSIGNED > CLI Synopsis[info,stats] need to be changed > ------------------------------------------- > > Key: ISPN-2850 > URL: https://issues.jboss.org/browse/ISPN-2850 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 5.2.2.Final > Reporter: Vitalii Chepeliuk > Assignee: Tristan Tarrant > Priority: Minor > Labels: testsuite_stability > Fix For: 5.2.3.Final, 5.3.0.Final > > > [disconnected//]> help info > SYNOPSIS > info [cachename] > > DESCRIPTION > Shows configuration information about the specified cache or about the active cache manager > > ARGUMENTS > cachename > (optional) the name of the cache for which the configuration will be printed. If omitted, the active cache manager's configuration will be shown > [disconnected//]> help s > site start stats > [disconnected//]> help stats > SYNOPSIS > info [cachename] > > DESCRIPTION > Shows information about the specified cache or about the active cache manager > > ARGUMENTS > cachename > (optional) the name of the cache for which information will be printed. If omitted, information about the active cache manager will be shown -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2013