July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3820) tx.totalorder.statetransfer.ReplTotalOrderStateTransferFunctional2PcTest randomly fails on RHEL5

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3820?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3820: ------------------------------- Labels: testsuite_stability (was: ) > tx.totalorder.statetransfer.ReplTotalOrderStateTransferFunctional2PcTest randomly fails on RHEL5 > ------------------------------------------------------------------------------------------------ > > Key: ISPN-3820 > URL: https://issues.jboss.org/browse/ISPN-3820 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Environment: OracleJDK7, RHEL5_x86 > OracleJDK7, RHEL5_x86_64 > OpenJDK6, RHEL5_x86 > OpenJDK6, RHEL5_x86_64 > Reporter: Vitalii Chepeliuk > Labels: testsuite_stability > > Following tests fail randomly > org.infinispan.tx.totalorder.statetransfer.ReplTotalOrderStateTransferFunctional2PcTest.testSTWithThirdWritingTxCache > rg.infinispan.tx.totalorder.statetransfer.ReplTotalOrderStateTransferFunctional2PcTest.testSTWithThirdWritingNonTxCache > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6831) Implement topology changes updates in Ruby client

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6831?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6831: -------------------------------------- Component/s: Integration > Implement topology changes updates in Ruby client > ------------------------------------------------- > > Key: ISPN-6831 > URL: https://issues.jboss.org/browse/ISPN-6831 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > > Hot Rod protocol is a binary, platform independent, protocol created to enable clients to communicate with Infinispan servers. Hot Rod protocol clients can receive, as part of operation responses, cluster topology update information. The aim of this task is to implement this logic in Hot Rod's Ruby client. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6830) Implement topology changes updates in Python client

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6830?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6830: -------------------------------------- Component/s: Integration > Implement topology changes updates in Python client > --------------------------------------------------- > > Key: ISPN-6830 > URL: https://issues.jboss.org/browse/ISPN-6830 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Reporter: Sebastian Łaskawiec > > Hot Rod protocol is a binary, platform independent, protocol created to enable clients to communicate with Infinispan servers. Hot Rod protocol clients can receive, as part of operation responses, cluster topology update information. The aim of this task is to implement this logic in Hot Rod's Python client. > See https://github.com/infinispan/python-client/issues/3 and https://github.com/infinispan/python-client/issues/4 for more info. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6731) Test configuration conversion tool for library mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6731?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-6731: ---------------------------------- Assignee: Anna Manukyan > Test configuration conversion tool for library mode > ---------------------------------------------------- > > Key: ISPN-6731 > URL: https://issues.jboss.org/browse/ISPN-6731 > Project: Infinispan > Issue Type: Task > Components: Configuration > Reporter: Anna Manukyan > Assignee: Anna Manukyan > Fix For: 9.0.0.Alpha3 > > > Add tests for infinispan configuration conversion tool. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6731) Test configuration conversion tool for library mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6731?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6731: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha3 Resolution: Done > Test configuration conversion tool for library mode > ---------------------------------------------------- > > Key: ISPN-6731 > URL: https://issues.jboss.org/browse/ISPN-6731 > Project: Infinispan > Issue Type: Task > Components: Configuration > Reporter: Anna Manukyan > Fix For: 9.0.0.Alpha3 > > > Add tests for infinispan configuration conversion tool. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6833) Visualization and tracing of messages between nodes

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6833: ----------------------------------------- Summary: Visualization and tracing of messages between nodes Key: ISPN-6833 URL: https://issues.jboss.org/browse/ISPN-6833 Project: Infinispan Issue Type: Feature Request Reporter: Sebastian Łaskawiec Note: There is a work in progress already happening: https://github.com/infinispan/infispector We know what kind of messages should be generated between nodes to perform specific operations - in theory -, still to debug problems of configuration or implementation on the whole stack (application + Infinispan + JGroups) we often need to look into the logs, having thousands of trace lines even when sampling for small periods of time. It would be very useful to have a way to automatically extrapolate the interesting patterns out of a running system, we could collect reliable information for example using (just ideas): * A custom JGroups protocol * Byteman to instrument JGroups for specific events (like network socket usage, or thresholds being reached in internal structures like resend tables or threadpool sizes) * Simple log file parsing The collected information could then be used to generate condensed reports highlighting the patterns being used in practice to compare them with expected patterns. I have two different kinds if output in mind: * A graphical visualization, showing the cluster nodes and a sequence of colored arrows showcasing what is being done * A short text representation, to be used by: ** automated tests to verify invariant expectations are not broken on code changes ** future possible tool to formally proof correctness / race conditions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6832) Proof of correctness for complex distributed patterns

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6832: ----------------------------------------- Summary: Proof of correctness for complex distributed patterns Key: ISPN-6832 URL: https://issues.jboss.org/browse/ISPN-6832 Project: Infinispan Issue Type: Feature Request Reporter: Sebastian Łaskawiec The core of Infinispan can be represented in very simple "primitives": a set of nodes send messages to each other. The fundamental rules are also relatively simple: * a message can't be received before it's sent * a message could be lost * a node could be killed at any time >From these basic building blocks one can start building some logical consequences: * messages sent to multiple nodes might arrive at different times * multiple messages sent to multiple nodes might be delivered in different order Some of these problems are resolved by JGroups - but even then it must be configured accordingly, meaning Infinispan' s usage of it is sensible to using the wrong method or flags. While the Java/Scala code in Infinispan is not overly complex, it's not suited for reasoning on the consequences of often-needed changes in the codebase. It would be very useful to be able to define patterns in an ad-hoc meta language, and provide a proof correctness of the patterns it uses, or at least proof the events it should avoid can not happen. A great help for the project would be to sketch such a language and try it out on some of the distribution schemes Infinispan uses to proof they are correct or identify flaws in correctness. In a second step (optional) one could build some tooling around this to provide automatic demonstration / simulation for proposed changes expressed in this meta language. The Promela language could be used for this purpose; so one could build tooling around it, try to apply it on Infinispan, and possibly work on ad-hoc extesions. See also previous proposal: "Visualization and tracing of messages between nodes" -> that would make it possible to trace the real Infinispan behaviour and then demonstrate it's correctness or identify problems before they happen. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6831) Implement topology changes updates in Ruby client

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6831: ----------------------------------------- Summary: Implement topology changes updates in Ruby client Key: ISPN-6831 URL: https://issues.jboss.org/browse/ISPN-6831 Project: Infinispan Issue Type: Feature Request Reporter: Sebastian Łaskawiec Hot Rod protocol is a binary, platform independent, protocol created to enable clients to communicate with Infinispan servers. Hot Rod protocol clients can receive, as part of operation responses, cluster topology update information. The aim of this task is to implement this logic in Hot Rod's Ruby client. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6830) Implement topology changes updates in Python client

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6830: ----------------------------------------- Summary: Implement topology changes updates in Python client Key: ISPN-6830 URL: https://issues.jboss.org/browse/ISPN-6830 Project: Infinispan Issue Type: Feature Request Reporter: Sebastian Łaskawiec Hot Rod protocol is a binary, platform independent, protocol created to enable clients to communicate with Infinispan servers. Hot Rod protocol clients can receive, as part of operation responses, cluster topology update information. The aim of this task is to implement this logic in Hot Rod's Python client. See https://github.com/infinispan/python-client/issues/3 and https://github.com/infinispan/python-client/issues/4 for more info. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4772) APIDistTest random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4772?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-4772. -------------------------------- Fix Version/s: 9.0.0.Alpha2 Resolution: Done No longer failing in master. > APIDistTest random failures > --------------------------- > > Key: ISPN-4772 > URL: https://issues.jboss.org/browse/ISPN-4772 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 9.0.0.Alpha2 > > > The lock acquisition timeout is too small, because the asynchronous TxCompletionNotificationCommand can easily be delayed by more than 100ms. > Failure in CI here: http://ci.infinispan.org/viewLog.html?buildId=12250&buildTypeId=bt8&tab=b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2016