[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-17552: -- Ignite Flags: Release Notes Required > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-43, ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-17552: -- Labels: iep-43 ise (was: ise) > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-43, ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-17552: -- Priority: Major (was: Minor) > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Assignee: Pavel Pereslegin >Priority: Major > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node !createSnapshot_nonCrd.PNG|width=426,height=212! 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node !createSnapshot_nonCrd.PNG|width=426,height=212! 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > !createSnapshot_nonCrd.PNG|width=426,height=212! > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Attachment: createSnapshotCrd.jp2 > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Attachment: (was: createSnapshotCrd.jp2) > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Attachment: error.log 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: 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. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) execute "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > 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. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) execute "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
