You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2017/09/08 12:55:00 UTC
[jira] [Commented] (IGNITE-6313) transaction hangs while node left
cluster
[ https://issues.apache.org/jira/browse/IGNITE-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158581#comment-16158581 ]
Semen Boikov commented on IGNITE-6313:
--------------------------------------
[~zstan],
Is it possible to convert reproduced in standard Ignite test (for example like IgniteCachePutRetryAbstractSelfTest)?
Thanks
> transaction hangs while node left cluster
> -----------------------------------------
>
> Key: IGNITE-6313
> URL: https://issues.apache.org/jira/browse/IGNITE-6313
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Stanilovsky Evgeny
> Assignee: Dmitriy Govorukhin
> Attachments: run.py, tpre.tar.gz, trun.tar.gz
>
>
> in attached reproducer there are 2 projects,
> first - tpre simple fills cache
> second - trun concurrently update cache values.
> expected behavior 100 or sometimes 99 numbers in output, but after several grid autorestart python script we found grid have no active transactions ...
> try to find time for pure ignite reproducer, but for now it need be run like :
> sequentially start:
> *java -jar tpre-1.0-SNAPSHOT-jar-with-dependencies.jar 1000
> java -jar trun-1.0-SNAPSHOT-jar-with-dependencies.jar 1000 20 1
> run.py*
> console with *trun* process will soon output something like : BBB that signals no transactions found.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)