Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-8000

Implicit transactions may not finish properly on unstable topology.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 2.4
    • 2.5
    • None
    • None

    Description

      Add default tx timeout [1] to IgniteCacheMultiTxLockSelfTest test configuration.

      [1] c.getTransactionConfiguration().setDefaultTxTimeout(100000);

      Looks like in some case remote tx is added to rolled back version (because partition is gone) and subsequent near request for the same tx to this node fails.

      This is not happen if timeouts are disabled because corresponding check is skipped.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ascherbakov Alexey Scherbakov
            ascherbakov Alexey Scherbakov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment