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

The snapshot error is not propagated to the initiating node if it is not the coordinator.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.13
    • 2.14
    • None
    • Fixed an issue where the snapshot error was not propagated to the initiating node.
    • Release Notes Required

    Description

      In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated.
      This is misleading that the snapshot was taken successfully.

      The problem concerns not only metrics, despite the error, the user future completes successfully and error does not reach the user.

      Reproducer:

        startGridsWithCache(2, dfltCacheCfg, CACHE_KEYS_RANGE);
      
        // Must fail, but on non-coordinator finishes successfully.
        grid(1).context().cache().context().snapshotMgr().createSnapshot(SNAPSHOT_NAME, "/bad/path").get();
      
        // Fails (as expected).
        grid(0).context().cache().context().snapshotMgr().createSnapshot(SNAPSHOT_NAME, "/bad/path").get();
      

      Attachments

        1. error.log
          13 kB
          Stepanov Ilya

        Activity

          People

            xtern Pavel Pereslegin
            stElias Stepanov Ilya
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m