You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/10/06 14:18:00 UTC
[jira] [Comment Edited] (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=16194641#comment-16194641 ]
Alexey Goncharuk edited comment on IGNITE-6313 at 10/6/17 2:17 PM:
-------------------------------------------------------------------
[~estanilovsky] If I extend the lockDetectionTimeout to 40 seconds, the test passes, so it looks like there is a failure detection timeout should be configured. Can you take a look?
was (Author: agoncharuk):
[~estanilovsky] If I extends the lockDetectionTimeout to 40 seconds, the test passes, so it looks like there is a failure detection timeout should be configured. Can you take a look?
> 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: Ilya Lantukh
> Attachments: run.py, tpre.tar.gz, trun.tar.gz, TxDeadLockOnNodeRestart.java
>
>
> 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)