[jira] [Updated] (IGNITE-17587) The "io.datastorage.StorageSize" metric shows incorrect values in case of multiple persistence dataregions
[
https://issues.apache.org/jira/browse/IGNITE-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17587:
-
Fix Version/s: 2.14
> The "io.datastorage.StorageSize" metric shows incorrect values in case of
> multiple persistence dataregions
> --
>
> Key: IGNITE-17587
> URL: https://issues.apache.org/jira/browse/IGNITE-17587
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: ise
> Fix For: 2.14
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The metric was broken after IGNITE-13207: it sets the value of the last group
> instead of the sum of all groups. See
> {{DataStorageMetricsImpl#onStorageSizeChanged}} for details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17587) The "io.datastorage.StorageSize" metric shows incorrect values in case of multiple persistence dataregions
[
https://issues.apache.org/jira/browse/IGNITE-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597942#comment-17597942
]
Amelchev Nikita commented on IGNITE-17587:
--
[~xtern], Could you take a look, please?
> The "io.datastorage.StorageSize" metric shows incorrect values in case of
> multiple persistence dataregions
> --
>
> Key: IGNITE-17587
> URL: https://issues.apache.org/jira/browse/IGNITE-17587
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The metric was broken after IGNITE-13207: it sets the value of the last group
> instead of the sum of all groups. See
> {{DataStorageMetricsImpl#onStorageSizeChanged}} for details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17587) The "io.datastorage.StorageSize" metric shows incorrect values in case of multiple persistence dataregions
[
https://issues.apache.org/jira/browse/IGNITE-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17587:
-
Labels: ise (was: )
> The "io.datastorage.StorageSize" metric shows incorrect values in case of
> multiple persistence dataregions
> --
>
> Key: IGNITE-17587
> URL: https://issues.apache.org/jira/browse/IGNITE-17587
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The metric was broken after IGNITE-13207: it sets the value of the last group
> instead of the sum of all groups. See
> {{DataStorageMetricsImpl#onStorageSizeChanged}} for details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17587) The "io.datastorage.StorageSize" metric shows incorrect values in case of multiple persistence dataregions
Amelchev Nikita created IGNITE-17587:
Summary: The "io.datastorage.StorageSize" metric shows incorrect
values in case of multiple persistence dataregions
Key: IGNITE-17587
URL: https://issues.apache.org/jira/browse/IGNITE-17587
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
The metric was broken after IGNITE-13207: it sets the value of the last group
instead of the sum of all groups. See
{{DataStorageMetricsImpl#onStorageSizeChanged}} for details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17452) [Extensions] Implement Kafka to thin client CDC streamer
[ https://issues.apache.org/jira/browse/IGNITE-17452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita reassigned IGNITE-17452: Assignee: Amelchev Nikita > [Extensions] Implement Kafka to thin client CDC streamer > > > Key: IGNITE-17452 > URL: https://issues.apache.org/jira/browse/IGNITE-17452 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-59, ise > > Implement Kafka to thin client CDC streamer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17581383#comment-17581383
]
Amelchev Nikita commented on IGNITE-13510:
--
Cherry-picked to the 2.14.
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: iep-43, ise, snapshot
> Fix For: 2.14
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Creating
> {noformat}
> Create snapshot operation is in progress.
> Snapshot name: snapshot1
> Operation ID: 0c636326-76f8-4918-b15c-1010d9c47a5f
> Started at: Aug 17, 2022 8:02:27 PM
> Duration: 00:00:00.734
> Estimated operation progress:
> Node ID Processed, bytesTotal, bytes
> Percent
> a4d3f584-bd67-4550-a26a-afa3bd54120.0 KB2.2 MB
> 5%
> ef3a27fd-86eb-4886-97e6-7b061f1116.6 MB 34.1 MB
> 48%
> ffd8a17e-1fa4-4671-aac6-e2a3447312.6 MB 34.4 MB
> 36%
> 072d4b79-d4f9-472e-8b6a-d05c34f2132.0 KB2.1 MB
> 6%
> 210db306-0aa9-45ef-a0ca-5b7f612016.7 MB 34.2 MB
> 48%
> {noformat}
> Restoring
> {noformat}
> Restore snapshot operation is in progress.
> Snapshot name: snapshot1
> Operation ID: 96201080-b1d0-4f0c-80ef-5e046c1f62cf
> Started at: Aug 17, 2022 8:02:30 PM
> Duration: 00:00:00.170
> Estimated operation progress:
> Node ID Processed, partitionsTotal,
> partitionsPercent
> a4d3f584-bd67-4550-a26a-afa3bd5499
> 100%
> ef3a27fd-86eb-4886-97e6-7b061f1111 16
> 68%
> ffd8a17e-1fa4-4671-aac6-e2a3447314 16
> 87%
> 072d4b79-d4f9-472e-8b6a-d05c34f211 12
> 91%
> 210db306-0aa9-45ef-a0ca-5b7f612012 16
> 75%
> {noformat}
> No snapshot operation
> {noformat}
> There is no create or restore snapshot operation in progress.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580908#comment-17580908
]
Amelchev Nikita commented on IGNITE-13510:
--
[~xtern], [~RyzhovSV], I have prepared
[PR|https://github.com/apache/ignite/pull/10202]. Could you take a look, please?
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: iep-43, ise, snapshot
> Fix For: 2.14
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Creating
> {noformat}
> Create snapshot operation is in progress.
> Snapshot name: snapshot1
> Operation ID: 0c636326-76f8-4918-b15c-1010d9c47a5f
> Started at: Aug 17, 2022 8:02:27 PM
> Duration: 00:00:00.734
> Estimated operation progress:
> Node ID Processed, bytesTotal, bytes
> Percent
> a4d3f584-bd67-4550-a26a-afa3bd54120.0 KB2.2 MB
> 5%
> ef3a27fd-86eb-4886-97e6-7b061f1116.6 MB 34.1 MB
> 48%
> ffd8a17e-1fa4-4671-aac6-e2a3447312.6 MB 34.4 MB
> 36%
> 072d4b79-d4f9-472e-8b6a-d05c34f2132.0 KB2.1 MB
> 6%
> 210db306-0aa9-45ef-a0ca-5b7f612016.7 MB 34.2 MB
> 48%
> {noformat}
> Restoring
> {noformat}
> Restore snapshot operation is in progress.
> Snapshot name: snapshot1
> Operation ID: 96201080-b1d0-4f0c-80ef-5e046c1f62cf
> Started at: Aug 17, 2022 8:02:30 PM
> Duration: 00:00:00.170
> Estimated operation progress:
> Node ID Processed, partitionsTotal,
> partitionsPercent
> a4d3f584-bd67-4550-a26a-afa3bd5499
> 100%
> ef3a27fd-86eb-4886-97e6-7b061f1111 16
> 68%
> ffd8a17e-1fa4-4671-aac6-e2a3447314 16
> 87%
> 072d4b79-d4f9-472e-8b6a-d05c34f211 12
> 91%
> 210db306-0aa9-45ef-a0ca-5b7f612012 16
> 75%
> {noformat}
> No snapshot operation
> {noformat}
> There is no create or restore snapshot operation in progress.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-13510:
-
Description:
the control.sh utility immediately relinquishes control
and without using metricExporter it is impossible to understand whether the
snapshot completed or not
Creating
{noformat}
Create snapshot operation is in progress.
Snapshot name: snapshot1
Operation ID: 0c636326-76f8-4918-b15c-1010d9c47a5f
Started at: Aug 17, 2022 8:02:27 PM
Duration: 00:00:00.734
Estimated operation progress:
Node ID Processed, bytesTotal, bytes
Percent
a4d3f584-bd67-4550-a26a-afa3bd54120.0 KB2.2 MB 5%
ef3a27fd-86eb-4886-97e6-7b061f1116.6 MB 34.1 MB 48%
ffd8a17e-1fa4-4671-aac6-e2a3447312.6 MB 34.4 MB 36%
072d4b79-d4f9-472e-8b6a-d05c34f2132.0 KB2.1 MB 6%
210db306-0aa9-45ef-a0ca-5b7f612016.7 MB 34.2 MB 48%
{noformat}
Restoring
{noformat}
Restore snapshot operation is in progress.
Snapshot name: snapshot1
Operation ID: 96201080-b1d0-4f0c-80ef-5e046c1f62cf
Started at: Aug 17, 2022 8:02:30 PM
Duration: 00:00:00.170
Estimated operation progress:
Node ID Processed, partitionsTotal,
partitionsPercent
a4d3f584-bd67-4550-a26a-afa3bd5499
100%
ef3a27fd-86eb-4886-97e6-7b061f1111 16
68%
ffd8a17e-1fa4-4671-aac6-e2a3447314 16
87%
072d4b79-d4f9-472e-8b6a-d05c34f211 12
91%
210db306-0aa9-45ef-a0ca-5b7f612012 16
75%
{noformat}
No snapshot operation
{noformat}
There is no create or restore snapshot operation in progress.
{noformat}
was:
the control.sh utility immediately relinquishes control
and without using metricExporter it is impossible to understand whether the
snapshot completed or not
Restoring
{code:java}
Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
2021 Copyright(C) Apache Software Foundation
User: sega
Time: 2021-10-07T14:18:59.523
Command [SNAPSHOT] started
Arguments: --snapshot status --yes
Status of SNAPSHOT operations:
gridCommandHandlerTest0 -> Restoring to snapshot with name: snapshot_02052020
gridCommandHandlerTest1 -> Restoring to snapshot with name: snapshot_02052020
Command [SNAPSHOT] finished with code: 0
Control utility has completed execution at: 2021-10-07T14:18:59.546
Execution time: 23 ms
{code}
Creating
{code:java}
Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
2021 Copyright(C) Apache Software Foundation
User: sega
Time: 2021-10-07T14:18:55.368
Command [SNAPSHOT] started
Arguments: --snapshot status --yes
Status of SNAPSHOT operations:
gridCommandHandlerTest0 -> Creating the snapshot with name: snapshot_02052020
gridCommandHandlerTest1 -> Creating the snapshot with name: snapshot_02052020
Command [SNAPSHOT] finished with code: 0
Control utility has completed execution at: 2021-10-07T14:18:55.391
Execution time: 23 ms
{code}
No snapshot operation
{code:java}
Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
2021 Copyright(C) Apache Software Foundation
User: sega
Time: 2021-10-07T14:18:58.408
Command [SNAPSHOT] started
Arguments: --snapshot status --yes
Status of SNAPSHOT operations:
gridCommandHandlerTest0 -> No snapshot operation.
gridCommandHandlerTest1 -> No snapshot operation.
Command [SNAPSHOT] finished with code: 0
Control utility has completed execution at: 2021-10-07T14:18:58.439
Execution time: 31 ms
{code}
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: iep-43, ise, snapshot
> Fix For: 2.14
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Creating
> {noformat}
> Create snapshot operation is in progress.
> Snapshot name: snapshot1
> Operation ID: 0c636326-76f8-4918-b15c-1010d9c47a5f
> Started at: Aug 17, 2022 8:02:27 PM
>
[jira] [Updated] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-13510:
-
Ignite Flags: Release Notes Required
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: iep-43, ise, snapshot
> Fix For: 2.14
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Restoring
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:59.523
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Restoring to snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Restoring to snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:59.546
> Execution time: 23 ms
> {code}
> Creating
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:55.368
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Creating the snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Creating the snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:55.391
> Execution time: 23 ms
> {code}
> No snapshot operation
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:58.408
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> No snapshot operation.
> gridCommandHandlerTest1 -> No snapshot operation.
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:58.439
> Execution time: 31 ms
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-13510:
-
Fix Version/s: 2.14
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: iep-43, ise, snapshot
> Fix For: 2.14
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Restoring
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:59.523
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Restoring to snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Restoring to snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:59.546
> Execution time: 23 ms
> {code}
> Creating
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:55.368
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Creating the snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Creating the snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:55.391
> Execution time: 23 ms
> {code}
> No snapshot operation
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:58.408
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> No snapshot operation.
> gridCommandHandlerTest1 -> No snapshot operation.
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:58.439
> Execution time: 31 ms
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita reassigned IGNITE-13510:
Assignee: Amelchev Nikita (was: Sergei Ryzhov)
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: iep-43, ise, snapshot
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Restoring
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:59.523
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Restoring to snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Restoring to snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:59.546
> Execution time: 23 ms
> {code}
> Creating
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:55.368
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Creating the snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Creating the snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:55.391
> Execution time: 23 ms
> {code}
> No snapshot operation
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:58.408
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> No snapshot operation.
> gridCommandHandlerTest1 -> No snapshot operation.
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:58.439
> Execution time: 31 ms
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578889#comment-17578889
]
Amelchev Nikita commented on IGNITE-13510:
--
[~RyzhovSV], Hi. Do you mind if I continue your work?
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: iep-43, ise, snapshot
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Restoring
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:59.523
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Restoring to snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Restoring to snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:59.546
> Execution time: 23 ms
> {code}
> Creating
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:55.368
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Creating the snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Creating the snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:55.391
> Execution time: 23 ms
> {code}
> No snapshot operation
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:58.408
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> No snapshot operation.
> gridCommandHandlerTest1 -> No snapshot operation.
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:58.439
> Execution time: 31 ms
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-17502) Tasks to sent the snapshot files are not ordered
[
https://issues.apache.org/jira/browse/IGNITE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578383#comment-17578383
]
Amelchev Nikita edited comment on IGNITE-17502 at 8/11/22 2:03 PM:
---
[~xtern], Hi. Could you take a look please?
was (Author: nsamelchev):
[~mmuzaf], Hi. Could you take a look please?
> Tasks to sent the snapshot files are not ordered
>
>
> Key: IGNITE-17502
> URL: https://issues.apache.org/jira/browse/IGNITE-17502
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: ise
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Tasks to sent the snapshot files are not ordered. This leads to socket
> timeout in a file sender while thread is busy by sending to other node:
> {noformat}
> sender.send(part1);
> ...
> otherSender.send(part3);
> ...
> // `sender` throws socket timeout exception.
> sender.send(part2);
> {noformat}
> {noformat}
> java.io.EOFException: null
> at
> java.io.ObjectInputStream$BlockDataInputStream.readBoolean(ObjectInputStream.java:3120)
> ~[?:1.8.0_201]
> at java.io.ObjectInputStream.readBoolean(ObjectInputStream.java:966)
> ~[?:1.8.0_201]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.receiveFromChannel(GridIoManager.java:2935)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processOpenedChannel(GridIoManager.java:2895)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:244)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:1237)
> [classes/:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_201]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_201]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]
> ...
> Caused by: org.apache.ignite.IgniteCheckedException: Requested topic is busy
> by another transmission. It's not allowed to process different sessions over
> the same topic simultaneously. Channel will be closed
> [initMsg=SessionChannelMessage
> [sesId=9c855b38281-d8dcd34f-916f-49d0-a453-cd1866acfce1],
> channel=java.nio.channels.SocketChannel[connected local=/127.0.0.1:47102
> remote=/127.0.0.1:55621], nodeId=5ace7280-b08a-4cf9-b428-7f70ef70]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processOpenedChannel(GridIoManager.java:2867)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:244)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:1237)
> ~[classes/:?]
> ... 3 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17502) Tasks to sent the snapshot files are not ordered
[
https://issues.apache.org/jira/browse/IGNITE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578383#comment-17578383
]
Amelchev Nikita commented on IGNITE-17502:
--
[~mmuzaf], Hi. Could you take a look please?
> Tasks to sent the snapshot files are not ordered
>
>
> Key: IGNITE-17502
> URL: https://issues.apache.org/jira/browse/IGNITE-17502
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: ise
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Tasks to sent the snapshot files are not ordered. This leads to socket
> timeout in a file sender while thread is busy by sending to other node:
> {noformat}
> sender.send(part1);
> ...
> otherSender.send(part3);
> ...
> // `sender` throws socket timeout exception.
> sender.send(part2);
> {noformat}
> {noformat}
> java.io.EOFException: null
> at
> java.io.ObjectInputStream$BlockDataInputStream.readBoolean(ObjectInputStream.java:3120)
> ~[?:1.8.0_201]
> at java.io.ObjectInputStream.readBoolean(ObjectInputStream.java:966)
> ~[?:1.8.0_201]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.receiveFromChannel(GridIoManager.java:2935)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processOpenedChannel(GridIoManager.java:2895)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:244)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:1237)
> [classes/:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_201]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_201]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]
> ...
> Caused by: org.apache.ignite.IgniteCheckedException: Requested topic is busy
> by another transmission. It's not allowed to process different sessions over
> the same topic simultaneously. Channel will be closed
> [initMsg=SessionChannelMessage
> [sesId=9c855b38281-d8dcd34f-916f-49d0-a453-cd1866acfce1],
> channel=java.nio.channels.SocketChannel[connected local=/127.0.0.1:47102
> remote=/127.0.0.1:55621], nodeId=5ace7280-b08a-4cf9-b428-7f70ef70]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processOpenedChannel(GridIoManager.java:2867)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:244)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:1237)
> ~[classes/:?]
> ... 3 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17503) Transmission sender fails if receiver's pool is busy.
Amelchev Nikita created IGNITE-17503:
Summary: Transmission sender fails if receiver's pool is busy.
Key: IGNITE-17503
URL: https://issues.apache.org/jira/browse/IGNITE-17503
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Reproducer:
{noformat}
// do as much as a pool size.
rcv.getExecutorService().submit(() -> doSleep(1));
try (TransmissionSender sender = openTransmissionSender(rcvNodeId)) {
sender.send(file1); // throws SocketTimeoutException
}
{noformat}
Exception:
{noformat}
java.net.SocketTimeoutException: null
at
sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:211)
~[?:1.8.0_201]
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103)
~[?:1.8.0_201]
at
java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2663)
~[?:1.8.0_201]
at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2679)
~[?:1.8.0_201]
at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
~[?:1.8.0_201]
at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
~[?:1.8.0_201]
at java.io.ObjectInputStream.(ObjectInputStream.java:358)
~[?:1.8.0_201]
at
org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.connect(GridIoManager.java:3262)
~[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3350)
[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3288)
[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest.testSendToBusy(GridIoManagerFileTransmissionSelfTest.java:967)
[test-classes/:?]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17502) Tasks to sent the snapshot files are not ordered
[
https://issues.apache.org/jira/browse/IGNITE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17502:
-
Description:
Tasks to sent the snapshot files are not ordered. This leads to socket timeout
in a file sender while thread is busy by sending to other node:
{noformat}
sender.send(part1);
...
otherSender.send(part3);
...
// `sender` throws socket timeout exception.
sender.send(part2);
{noformat}
{noformat}
java.io.EOFException: null
at
java.io.ObjectInputStream$BlockDataInputStream.readBoolean(ObjectInputStream.java:3120)
~[?:1.8.0_201]
at java.io.ObjectInputStream.readBoolean(ObjectInputStream.java:966)
~[?:1.8.0_201]
at
org.apache.ignite.internal.managers.communication.GridIoManager.receiveFromChannel(GridIoManager.java:2935)
[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManager.processOpenedChannel(GridIoManager.java:2895)
[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:244)
[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:1237)
[classes/:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_201]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_201]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]
...
Caused by: org.apache.ignite.IgniteCheckedException: Requested topic is busy by
another transmission. It's not allowed to process different sessions over the
same topic simultaneously. Channel will be closed
[initMsg=SessionChannelMessage
[sesId=9c855b38281-d8dcd34f-916f-49d0-a453-cd1866acfce1],
channel=java.nio.channels.SocketChannel[connected local=/127.0.0.1:47102
remote=/127.0.0.1:55621], nodeId=5ace7280-b08a-4cf9-b428-7f70ef70]
at
org.apache.ignite.internal.managers.communication.GridIoManager.processOpenedChannel(GridIoManager.java:2867)
~[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:244)
~[classes/:?]
at
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:1237)
~[classes/:?]
... 3 more
{noformat}
was:
Tasks to sent the snapshot files are not ordered. This leads to socket timeout
in a file sender while thread is busy by sending to other node:
{noformat}
sender.send(part1);
...
otherSender.send(part3);
...
// `sender` throws socket timeout exception.
sender.send(part2);
{noformat}
> Tasks to sent the snapshot files are not ordered
>
>
> Key: IGNITE-17502
> URL: https://issues.apache.org/jira/browse/IGNITE-17502
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: ise
> Fix For: 2.14
>
>
> Tasks to sent the snapshot files are not ordered. This leads to socket
> timeout in a file sender while thread is busy by sending to other node:
> {noformat}
> sender.send(part1);
> ...
> otherSender.send(part3);
> ...
> // `sender` throws socket timeout exception.
> sender.send(part2);
> {noformat}
> {noformat}
> java.io.EOFException: null
> at
> java.io.ObjectInputStream$BlockDataInputStream.readBoolean(ObjectInputStream.java:3120)
> ~[?:1.8.0_201]
> at java.io.ObjectInputStream.readBoolean(ObjectInputStream.java:966)
> ~[?:1.8.0_201]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.receiveFromChannel(GridIoManager.java:2935)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processOpenedChannel(GridIoManager.java:2895)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:244)
> [classes/:?]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:1237)
> [classes/:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_201]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_201]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]
> ...
> Caused by: org.apache.ignite.IgniteCheckedException: Requested topic is busy
> by another transmission. It's not allowed to process different sessions over
> the same topic simultaneously. Channel will be closed
> [initMsg=SessionChannelMessage
> [sesId=9c855b38281-d8dcd34f-916f-49d0-a453-cd1866acfce1],
> channel=java.nio.channels.SocketChannel[connected local=/127.0.0.1:47102
> remote=/127.0.0.1:55621],
[jira] [Updated] (IGNITE-17502) Tasks to sent the snapshot files are not ordered
[
https://issues.apache.org/jira/browse/IGNITE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17502:
-
Fix Version/s: 2.14
> Tasks to sent the snapshot files are not ordered
>
>
> Key: IGNITE-17502
> URL: https://issues.apache.org/jira/browse/IGNITE-17502
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.14
>
>
> Tasks to sent the snapshot files are not ordered. This leads to socket
> timeout in a file sender while thread is busy by sending to other node:
> {noformat}
> sender.send(part1);
> ...
> otherSender.send(part3);
> ...
> // `sender` throws socket timeout exception.
> sender.send(part2);
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17502) Tasks to sent the snapshot files are not ordered
[
https://issues.apache.org/jira/browse/IGNITE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17502:
-
Labels: ise (was: )
> Tasks to sent the snapshot files are not ordered
>
>
> Key: IGNITE-17502
> URL: https://issues.apache.org/jira/browse/IGNITE-17502
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: ise
> Fix For: 2.14
>
>
> Tasks to sent the snapshot files are not ordered. This leads to socket
> timeout in a file sender while thread is busy by sending to other node:
> {noformat}
> sender.send(part1);
> ...
> otherSender.send(part3);
> ...
> // `sender` throws socket timeout exception.
> sender.send(part2);
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17502) Tasks to sent the snapshot files are not ordered
Amelchev Nikita created IGNITE-17502:
Summary: Tasks to sent the snapshot files are not ordered
Key: IGNITE-17502
URL: https://issues.apache.org/jira/browse/IGNITE-17502
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
Tasks to sent the snapshot files are not ordered. This leads to socket timeout
in a file sender while thread is busy by sending to other node:
{noformat}
sender.send(part1);
...
otherSender.send(part3);
...
// `sender` throws socket timeout exception.
sender.send(part2);
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17450) Documentation: thin client CDC streamer
[ https://issues.apache.org/jira/browse/IGNITE-17450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17450: - Component/s: documentation > Documentation: thin client CDC streamer > --- > > Key: IGNITE-17450 > URL: https://issues.apache.org/jira/browse/IGNITE-17450 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Minor > Labels: IEP-59 > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Add thin client CDC streamer documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17450) Documentation: thin client CDC streamer
[ https://issues.apache.org/jira/browse/IGNITE-17450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17450: - Labels: IEP-59 ise (was: IEP-59) > Documentation: thin client CDC streamer > --- > > Key: IGNITE-17450 > URL: https://issues.apache.org/jira/browse/IGNITE-17450 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Add thin client CDC streamer documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17450) Documentation: thin client CDC streamer
[ https://issues.apache.org/jira/browse/IGNITE-17450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17450: - Fix Version/s: 2.14 > Documentation: thin client CDC streamer > --- > > Key: IGNITE-17450 > URL: https://issues.apache.org/jira/browse/IGNITE-17450 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Minor > Labels: IEP-59 > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Add thin client CDC streamer documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17451) Provide internal access to BinaryContext in thin client
[ https://issues.apache.org/jira/browse/IGNITE-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17451: - Description: Provide internal access to BinaryContext in thin client. (was: Implement thin client CDC streamer metadata replication) > Provide internal access to BinaryContext in thin client > --- > > Key: IGNITE-17451 > URL: https://issues.apache.org/jira/browse/IGNITE-17451 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-59, ise > Fix For: 2.14 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Provide internal access to BinaryContext in thin client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17451) Provide internal access to BinaryContext in thin client
[ https://issues.apache.org/jira/browse/IGNITE-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17451: - Summary: Provide internal access to BinaryContext in thin client (was: Implement thin client CDC streamer metadata replication) > Provide internal access to BinaryContext in thin client > --- > > Key: IGNITE-17451 > URL: https://issues.apache.org/jira/browse/IGNITE-17451 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-59, ise > Fix For: 2.14 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Implement thin client CDC streamer metadata replication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17451) [Extensions] Implement thin client CDC streamer metadata replication
[ https://issues.apache.org/jira/browse/IGNITE-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17451: - Ignite Flags: (was: Docs Required,Release Notes Required) > [Extensions] Implement thin client CDC streamer metadata replication > > > Key: IGNITE-17451 > URL: https://issues.apache.org/jira/browse/IGNITE-17451 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-59, ise > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement thin client CDC streamer metadata replication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17451) Implement thin client CDC streamer metadata replication
[ https://issues.apache.org/jira/browse/IGNITE-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17451: - Summary: Implement thin client CDC streamer metadata replication (was: [Extensions] Implement thin client CDC streamer metadata replication) > Implement thin client CDC streamer metadata replication > --- > > Key: IGNITE-17451 > URL: https://issues.apache.org/jira/browse/IGNITE-17451 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-59, ise > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement thin client CDC streamer metadata replication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17451) [Extensions] Implement thin client CDC streamer metadata replication
[ https://issues.apache.org/jira/browse/IGNITE-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17451: - Fix Version/s: 2.14 > [Extensions] Implement thin client CDC streamer metadata replication > > > Key: IGNITE-17451 > URL: https://issues.apache.org/jira/browse/IGNITE-17451 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-59, ise > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement thin client CDC streamer metadata replication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17452) [Extensions] Implement Kafka to thin client CDC streamer
Amelchev Nikita created IGNITE-17452: Summary: [Extensions] Implement Kafka to thin client CDC streamer Key: IGNITE-17452 URL: https://issues.apache.org/jira/browse/IGNITE-17452 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Implement Kafka to thin client CDC streamer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16743) [Extensions] Implement thin client CDC streamer
[ https://issues.apache.org/jira/browse/IGNITE-16743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16743: - Labels: IEP-59 ise (was: ise) > [Extensions] Implement thin client CDC streamer > --- > > Key: IGNITE-16743 > URL: https://issues.apache.org/jira/browse/IGNITE-16743 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-59, ise > > Implement consumer that streams all data changes to thin client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17451) [Extensions] Implement thin client CDC streamer metadata replication
Amelchev Nikita created IGNITE-17451: Summary: [Extensions] Implement thin client CDC streamer metadata replication Key: IGNITE-17451 URL: https://issues.apache.org/jira/browse/IGNITE-17451 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Implement thin client CDC streamer metadata replication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17451) [Extensions] Implement thin client CDC streamer metadata replication
[ https://issues.apache.org/jira/browse/IGNITE-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17451: - Labels: ise (was: ) > [Extensions] Implement thin client CDC streamer metadata replication > > > Key: IGNITE-17451 > URL: https://issues.apache.org/jira/browse/IGNITE-17451 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: ise > > Implement thin client CDC streamer metadata replication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17450) Documentation: thin client CDC streamer
Amelchev Nikita created IGNITE-17450: Summary: Documentation: thin client CDC streamer Key: IGNITE-17450 URL: https://issues.apache.org/jira/browse/IGNITE-17450 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add thin client CDC streamer documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17449) CDC: investigate eviction policy of entries
[
https://issues.apache.org/jira/browse/IGNITE-17449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita reassigned IGNITE-17449:
Assignee: Amelchev Nikita
> CDC: investigate eviction policy of entries
> ---
>
> Key: IGNITE-17449
> URL: https://issues.apache.org/jira/browse/IGNITE-17449
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: ise
>
> The eviction policy can be set not only by configuration but via
> {{IgniteCache#withExpiryPolicy}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17449) CDC: investigate eviction policy of entries
[
https://issues.apache.org/jira/browse/IGNITE-17449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17449:
-
Labels: ise (was: )
> CDC: investigate eviction policy of entries
> ---
>
> Key: IGNITE-17449
> URL: https://issues.apache.org/jira/browse/IGNITE-17449
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Priority: Major
> Labels: ise
>
> The eviction policy can be set not only by configuration but via
> {{IgniteCache#withExpiryPolicy}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17449) CDC: investigate eviction policy of entries
Amelchev Nikita created IGNITE-17449:
Summary: CDC: investigate eviction policy of entries
Key: IGNITE-17449
URL: https://issues.apache.org/jira/browse/IGNITE-17449
Project: Ignite
Issue Type: Task
Reporter: Amelchev Nikita
The eviction policy can be set not only by configuration but via
{{IgniteCache#withExpiryPolicy}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17407) The snapshot rate limit does not work correctly when set to values greater than 100 MB per second.
[
https://issues.apache.org/jira/browse/IGNITE-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572468#comment-17572468
]
Amelchev Nikita commented on IGNITE-17407:
--
[~xtern], LGTM.
> The snapshot rate limit does not work correctly when set to values greater
> than 100 MB per second.
>
>
> Key: IGNITE-17407
> URL: https://issues.apache.org/jira/browse/IGNITE-17407
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The snapshot rate limit does not work correctly when set to values greater
> than 100 MB per second.
> Currently, the snapshot transfer rate is limited by the BasicRateLimiter.
> Testing shows that limiter is unable to give more than ~119 millions permits
> per second.
> {code:java}
> long dataSize = U.GB;
> BasicRateLimiter limiter = new BasicRateLimiter(dataSize / 2);
> int blockSize =
> IgniteSnapshotManager.SNAPSHOT_LIMITED_TRANSFER_BLOCK_SIZE_BYTES;
> long start = System.currentTimeMillis();
> for (long i = 0; i < dataSize; i+=blockSize)
> limiter.acquire(blockSize);
> long totalSec =
> TimeUnit.MILLISECONDS.toSeconds(System.currentTimeMillis() - start);
> System.out.println("Speed= " + (dataSize / totalSec));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17
[
https://issues.apache.org/jira/browse/IGNITE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569348#comment-17569348
]
Amelchev Nikita commented on IGNITE-16650:
--
Merged into the master.
[~RyzhovSV], thank you for the initial contribution!
[~PetrovMikhail], thank you for the contribution!
> Exclude ignite-log4j, log4j 1.2.17
> --
>
> Key: IGNITE-16650
> URL: https://issues.apache.org/jira/browse/IGNITE-16650
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergei Ryzhov
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: important, ise
> Fix For: 2.14
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> log4j 1.2.17 is not supported and contains critical vulnerabilities
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> I suggest excluding the ignite-log4j module from ignite
> Direct vulnerabilities:
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
> As a result of the mentioned migration, the following changes will be applied:
> 1. ignite-log4j.xml will be migrated to log4j2 format. Unfortunately after
> the refactoring we will get two configuration ignite-log4j.xml and
> ignite-log4j2.xml both in log4j2 format because ignite-log4j2.xml is in use
> now and but provide log formatitng different from ignite-log4j.xml.
> 2. core/src/test/config/log4j-test.xml will not be migrated to log4j2 because
> it is used with compatibility tests.
> 3. core/src/test/config/log4j2-test.xml is refactored to suite current log4j
> format. The current version of core/src/test/config/log4j2-test.xml is
> moved to the log4j2/src/test/config folder.
> 4. osgi-paxlogging will be removed because it's only meant to provide some
> log4j dependencies. We have no need in them now.
> 5. Exception logging format will change slightly:
> Before:
> {code:java}
> class org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> After:
> {code:java}
> org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> As you can see, only the first word "class" is omitted.
> 6. All other files containing log4j configuration will be refactored to suite
> log4j2 and will be renamed if previously their name allowed log4j to
> automatically find them in the class path (e.g. log4j.xml -> log4j2.xml and
> so on)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17
[
https://issues.apache.org/jira/browse/IGNITE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita resolved IGNITE-16650.
--
Release Note: Removed deprecated log4j 1.x module
Resolution: Fixed
> Exclude ignite-log4j, log4j 1.2.17
> --
>
> Key: IGNITE-16650
> URL: https://issues.apache.org/jira/browse/IGNITE-16650
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergei Ryzhov
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: important, ise
> Fix For: 2.14
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> log4j 1.2.17 is not supported and contains critical vulnerabilities
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> I suggest excluding the ignite-log4j module from ignite
> Direct vulnerabilities:
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
> As a result of the mentioned migration, the following changes will be applied:
> 1. ignite-log4j.xml will be migrated to log4j2 format. Unfortunately after
> the refactoring we will get two configuration ignite-log4j.xml and
> ignite-log4j2.xml both in log4j2 format because ignite-log4j2.xml is in use
> now and but provide log formatitng different from ignite-log4j.xml.
> 2. core/src/test/config/log4j-test.xml will not be migrated to log4j2 because
> it is used with compatibility tests.
> 3. core/src/test/config/log4j2-test.xml is refactored to suite current log4j
> format. The current version of core/src/test/config/log4j2-test.xml is
> moved to the log4j2/src/test/config folder.
> 4. osgi-paxlogging will be removed because it's only meant to provide some
> log4j dependencies. We have no need in them now.
> 5. Exception logging format will change slightly:
> Before:
> {code:java}
> class org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> After:
> {code:java}
> org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> As you can see, only the first word "class" is omitted.
> 6. All other files containing log4j configuration will be refactored to suite
> log4j2 and will be renamed if previously their name allowed log4j to
> automatically find them in the class path (e.g. log4j.xml -> log4j2.xml and
> so on)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17
[
https://issues.apache.org/jira/browse/IGNITE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-16650:
-
Labels: important ise (was: ise)
> Exclude ignite-log4j, log4j 1.2.17
> --
>
> Key: IGNITE-16650
> URL: https://issues.apache.org/jira/browse/IGNITE-16650
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergei Ryzhov
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: important, ise
> Fix For: 2.14
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> log4j 1.2.17 is not supported and contains critical vulnerabilities
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> I suggest excluding the ignite-log4j module from ignite
> Direct vulnerabilities:
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
> As a result of the mentioned migration, the following changes will be applied:
> 1. ignite-log4j.xml will be migrated to log4j2 format. Unfortunately after
> the refactoring we will get two configuration ignite-log4j.xml and
> ignite-log4j2.xml both in log4j2 format because ignite-log4j2.xml is in use
> now and but provide log formatitng different from ignite-log4j.xml.
> 2. core/src/test/config/log4j-test.xml will not be migrated to log4j2 because
> it is used with compatibility tests.
> 3. core/src/test/config/log4j2-test.xml is refactored to suite current log4j
> format. The current version of core/src/test/config/log4j2-test.xml is
> moved to the log4j2/src/test/config folder.
> 4. osgi-paxlogging will be removed because it's only meant to provide some
> log4j dependencies. We have no need in them now.
> 5. Exception logging format will change slightly:
> Before:
> {code:java}
> class org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> After:
> {code:java}
> org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> As you can see, only the first word "class" is omitted.
> 6. All other files containing log4j configuration will be refactored to suite
> log4j2 and will be renamed if previously their name allowed log4j to
> automatically find them in the class path (e.g. log4j.xml -> log4j2.xml and
> so on)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17
[
https://issues.apache.org/jira/browse/IGNITE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-16650:
-
Issue Type: Improvement (was: Bug)
> Exclude ignite-log4j, log4j 1.2.17
> --
>
> Key: IGNITE-16650
> URL: https://issues.apache.org/jira/browse/IGNITE-16650
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergei Ryzhov
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: important, ise
> Fix For: 2.14
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> log4j 1.2.17 is not supported and contains critical vulnerabilities
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> I suggest excluding the ignite-log4j module from ignite
> Direct vulnerabilities:
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
> As a result of the mentioned migration, the following changes will be applied:
> 1. ignite-log4j.xml will be migrated to log4j2 format. Unfortunately after
> the refactoring we will get two configuration ignite-log4j.xml and
> ignite-log4j2.xml both in log4j2 format because ignite-log4j2.xml is in use
> now and but provide log formatitng different from ignite-log4j.xml.
> 2. core/src/test/config/log4j-test.xml will not be migrated to log4j2 because
> it is used with compatibility tests.
> 3. core/src/test/config/log4j2-test.xml is refactored to suite current log4j
> format. The current version of core/src/test/config/log4j2-test.xml is
> moved to the log4j2/src/test/config folder.
> 4. osgi-paxlogging will be removed because it's only meant to provide some
> log4j dependencies. We have no need in them now.
> 5. Exception logging format will change slightly:
> Before:
> {code:java}
> class org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> After:
> {code:java}
> org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> As you can see, only the first word "class" is omitted.
> 6. All other files containing log4j configuration will be refactored to suite
> log4j2 and will be renamed if previously their name allowed log4j to
> automatically find them in the class path (e.g. log4j.xml -> log4j2.xml and
> so on)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17
[
https://issues.apache.org/jira/browse/IGNITE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-16650:
-
Fix Version/s: 2.14
> Exclude ignite-log4j, log4j 1.2.17
> --
>
> Key: IGNITE-16650
> URL: https://issues.apache.org/jira/browse/IGNITE-16650
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergei Ryzhov
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: ise
> Fix For: 2.14
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> log4j 1.2.17 is not supported and contains critical vulnerabilities
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> I suggest excluding the ignite-log4j module from ignite
> Direct vulnerabilities:
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
> As a result of the mentioned migration, the following changes will be applied:
> 1. ignite-log4j.xml will be migrated to log4j2 format. Unfortunately after
> the refactoring we will get two configuration ignite-log4j.xml and
> ignite-log4j2.xml both in log4j2 format because ignite-log4j2.xml is in use
> now and but provide log formatitng different from ignite-log4j.xml.
> 2. core/src/test/config/log4j-test.xml will not be migrated to log4j2 because
> it is used with compatibility tests.
> 3. core/src/test/config/log4j2-test.xml is refactored to suite current log4j
> format. The current version of core/src/test/config/log4j2-test.xml is
> moved to the log4j2/src/test/config folder.
> 4. osgi-paxlogging will be removed because it's only meant to provide some
> log4j dependencies. We have no need in them now.
> 5. Exception logging format will change slightly:
> Before:
> {code:java}
> class org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> After:
> {code:java}
> org.apache.ignite.IgniteException: Platform error:System.Exception:
> EXCEPTION_TEST_Warn
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:449)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:511)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:575)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> {code}
> As you can see, only the first word "class" is omitted.
> 6. All other files containing log4j configuration will be refactored to suite
> log4j2 and will be renamed if previously their name allowed log4j to
> automatically find them in the class path (e.g. log4j.xml -> log4j2.xml and
> so on)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17326) Update Ignite dependency: Spring
[ https://issues.apache.org/jira/browse/IGNITE-17326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17326: - Release Note: Updated Spring dependency to 5.2.22 (was: Update Spring dependency to 5.2.22) > Update Ignite dependency: Spring > > > Key: IGNITE-17326 > URL: https://issues.apache.org/jira/browse/IGNITE-17326 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update Ignite dependency Spring 5.2.21.RELEASE to 5.2.22.RELEASE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17326) Update Ignite dependency: Spring
[ https://issues.apache.org/jira/browse/IGNITE-17326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17326: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: Spring > > > Key: IGNITE-17326 > URL: https://issues.apache.org/jira/browse/IGNITE-17326 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update Ignite dependency Spring 5.2.21.RELEASE to 5.2.22.RELEASE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17323) Update Ignite dependency: Jetty
[ https://issues.apache.org/jira/browse/IGNITE-17323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17323: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: Jetty > --- > > Key: IGNITE-17323 > URL: https://issues.apache.org/jira/browse/IGNITE-17323 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update Jetty dependency 9.4.39.v20210325 to 9.4.43.v20210629 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564282#comment-17564282 ] Amelchev Nikita commented on IGNITE-13570: -- [~mmuzaf], LGTM. > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task > Components: extensions >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17311) KafkaToIgniteLoader instantiates several Spring contexts
[ https://issues.apache.org/jira/browse/IGNITE-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17311: - Fix Version/s: 2.14 > KafkaToIgniteLoader instantiates several Spring contexts > > > Key: IGNITE-17311 > URL: https://issues.apache.org/jira/browse/IGNITE-17311 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.14 > > > KafkaToIgniteLoader instantiates two SpringApplicationContext during app > start. > This can lead to error in case other beans inside context not designed for > this case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17315) [Extensions] Fix topology-validator-ext compilation
[
https://issues.apache.org/jira/browse/IGNITE-17315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita resolved IGNITE-17315.
--
Resolution: Fixed
> [Extensions] Fix topology-validator-ext compilation
> ---
>
> Key: IGNITE-17315
> URL: https://issues.apache.org/jira/browse/IGNITE-17315
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>
> {noformat}
> 05:05:05 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project ignite-topology-validator-ext: Compilation
> failure: Compilation failure:
> 05:05:05 [ERROR]
> /opt/buildagent/work/9319dd66c384518/modules/topology-validator-ext/src/test/java/org/apache/ignite/plugin/cache/IgniteCacheTopologyValidatorTest.java:[43,53]
> cannot find symbol
> 05:05:05 [ERROR] symbol: class RunnableX
> 05:05:05 [ERROR] location: class
> org.apache.ignite.testframework.GridTestUtils
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17315) [Extensions] Fix topology-validator-ext compilation
[
https://issues.apache.org/jira/browse/IGNITE-17315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563158#comment-17563158
]
Amelchev Nikita commented on IGNITE-17315:
--
Merged into the master.
> [Extensions] Fix topology-validator-ext compilation
> ---
>
> Key: IGNITE-17315
> URL: https://issues.apache.org/jira/browse/IGNITE-17315
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>
> {noformat}
> 05:05:05 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project ignite-topology-validator-ext: Compilation
> failure: Compilation failure:
> 05:05:05 [ERROR]
> /opt/buildagent/work/9319dd66c384518/modules/topology-validator-ext/src/test/java/org/apache/ignite/plugin/cache/IgniteCacheTopologyValidatorTest.java:[43,53]
> cannot find symbol
> 05:05:05 [ERROR] symbol: class RunnableX
> 05:05:05 [ERROR] location: class
> org.apache.ignite.testframework.GridTestUtils
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17315) [Extensions] Fix topology-validator-ext compilation
[
https://issues.apache.org/jira/browse/IGNITE-17315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563157#comment-17563157
]
Amelchev Nikita commented on IGNITE-17315:
--
https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_TopologyValidator/6669220
> [Extensions] Fix topology-validator-ext compilation
> ---
>
> Key: IGNITE-17315
> URL: https://issues.apache.org/jira/browse/IGNITE-17315
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>
> {noformat}
> 05:05:05 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project ignite-topology-validator-ext: Compilation
> failure: Compilation failure:
> 05:05:05 [ERROR]
> /opt/buildagent/work/9319dd66c384518/modules/topology-validator-ext/src/test/java/org/apache/ignite/plugin/cache/IgniteCacheTopologyValidatorTest.java:[43,53]
> cannot find symbol
> 05:05:05 [ERROR] symbol: class RunnableX
> 05:05:05 [ERROR] location: class
> org.apache.ignite.testframework.GridTestUtils
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17315) [Extensions] Fix topology-validator-ext compilation
Amelchev Nikita created IGNITE-17315:
Summary: [Extensions] Fix topology-validator-ext compilation
Key: IGNITE-17315
URL: https://issues.apache.org/jira/browse/IGNITE-17315
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
{noformat}
05:05:05 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
(default-testCompile) on project ignite-topology-validator-ext: Compilation
failure: Compilation failure:
05:05:05 [ERROR]
/opt/buildagent/work/9319dd66c384518/modules/topology-validator-ext/src/test/java/org/apache/ignite/plugin/cache/IgniteCacheTopologyValidatorTest.java:[43,53]
cannot find symbol
05:05:05 [ERROR] symbol: class RunnableX
05:05:05 [ERROR] location: class
org.apache.ignite.testframework.GridTestUtils
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17315) [Extensions] Fix topology-validator-ext compilation
[
https://issues.apache.org/jira/browse/IGNITE-17315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17315:
-
Component/s: extensions
> [Extensions] Fix topology-validator-ext compilation
> ---
>
> Key: IGNITE-17315
> URL: https://issues.apache.org/jira/browse/IGNITE-17315
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>
> {noformat}
> 05:05:05 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project ignite-topology-validator-ext: Compilation
> failure: Compilation failure:
> 05:05:05 [ERROR]
> /opt/buildagent/work/9319dd66c384518/modules/topology-validator-ext/src/test/java/org/apache/ignite/plugin/cache/IgniteCacheTopologyValidatorTest.java:[43,53]
> cannot find symbol
> 05:05:05 [ERROR] symbol: class RunnableX
> 05:05:05 [ERROR] location: class
> org.apache.ignite.testframework.GridTestUtils
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17311) KafkaToIgniteLoader instantiates several Spring contexts
[ https://issues.apache.org/jira/browse/IGNITE-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17311: - Component/s: extensions > KafkaToIgniteLoader instantiates several Spring contexts > > > Key: IGNITE-17311 > URL: https://issues.apache.org/jira/browse/IGNITE-17311 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > > KafkaToIgniteLoader instantiates two SpringApplicationContext during app > start. > This can lead to error in case other beans inside context not designed for > this case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17311) KafkaToIgniteLoader instantiates several Spring contexts
Amelchev Nikita created IGNITE-17311: Summary: KafkaToIgniteLoader instantiates several Spring contexts Key: IGNITE-17311 URL: https://issues.apache.org/jira/browse/IGNITE-17311 Project: Ignite Issue Type: Improvement Reporter: Amelchev Nikita Assignee: Amelchev Nikita KafkaToIgniteLoader instantiates two SpringApplicationContext during app start. This can lead to error in case other beans inside context not designed for this case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17294) Fix flaky test SqlViewExporterSpiTest#testComputeBroadcast
Amelchev Nikita created IGNITE-17294:
Summary: Fix flaky test SqlViewExporterSpiTest#testComputeBroadcast
Key: IGNITE-17294
URL: https://issues.apache.org/jira/browse/IGNITE-17294
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
The compute task finishes before a view query execution due to an error on
not-local node:
{noformat}
Caused by: java.lang.IllegalMonitorStateException
at
java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151)
...
org.apache.ignite.internal.processors.cache.metric.SqlViewExporterSpiTest.lambda$testComputeBroadcast$450c1f96$1(SqlViewExporterSpiTest.java:237)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17277) Add a user info to the sql queries view
[ https://issues.apache.org/jira/browse/IGNITE-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17277: - Description: Add a user info who started a query to the queries system view. > Add a user info to the sql queries view > > > Key: IGNITE-17277 > URL: https://issues.apache.org/jira/browse/IGNITE-17277 > Project: Ignite > Issue Type: Improvement >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add a user info who started a query to the queries system view. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17277) Add a user info to the sql queries view
[ https://issues.apache.org/jira/browse/IGNITE-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17277: - Environment: (was: Add a user info who started a query to the queries system view.) > Add a user info to the sql queries view > > > Key: IGNITE-17277 > URL: https://issues.apache.org/jira/browse/IGNITE-17277 > Project: Ignite > Issue Type: Improvement >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17277) Add a user info to the sql queries view
Amelchev Nikita created IGNITE-17277: Summary: Add a user info to the sql queries view Key: IGNITE-17277 URL: https://issues.apache.org/jira/browse/IGNITE-17277 Project: Ignite Issue Type: Improvement Environment: Add a user info who started a query to the queries system view. Reporter: Amelchev Nikita Assignee: Amelchev Nikita -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17218) Add isRequired flag for SpringResource annotation
[ https://issues.apache.org/jira/browse/IGNITE-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-17218. -- Release Note: Added support of optional beans for SpringResource annotation injection Resolution: Fixed Merged into the master. [~PetrovMikhail], thank you for the contribution. [~xtern], thanks for the review. > Add isRequired flag for SpringResource annotation > - > > Key: IGNITE-17218 > URL: https://issues.apache.org/jira/browse/IGNITE-17218 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > We need to add isRequired flag for SpringResource annotation that allows to > make some injection beans optional. Currently user will face exception if no > bean with specified name or type is defined in a Spring Context. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17218) Add isRequired flag for SpringResource annotation
[ https://issues.apache.org/jira/browse/IGNITE-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17218: - Fix Version/s: 2.14 > Add isRequired flag for SpringResource annotation > - > > Key: IGNITE-17218 > URL: https://issues.apache.org/jira/browse/IGNITE-17218 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > We need to add isRequired flag for SpringResource annotation that allows to > make some injection beans optional. Currently user will face exception if no > bean with specified name or type is defined in a Spring Context. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17086) SQL: long query warning not printed for lazy queries
[ https://issues.apache.org/jira/browse/IGNITE-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17086: - Priority: Minor (was: Major) > SQL: long query warning not printed for lazy queries > > > Key: IGNITE-17086 > URL: https://issues.apache.org/jira/browse/IGNITE-17086 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Priority: Minor > Labels: ise > Attachments: LongQueryWarningTest.java > > > Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17178) Notify preconfigured event listeners about node start after resources were injected.
[ https://issues.apache.org/jira/browse/IGNITE-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17178: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Notify preconfigured event listeners about node start after resources were > injected. > > > Key: IGNITE-17178 > URL: https://issues.apache.org/jira/browse/IGNITE-17178 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > We need to notify preconfigured event listeners about node start after > resources were injected. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17178) Notify preconfigured event listeners about node start after resources were injected.
[ https://issues.apache.org/jira/browse/IGNITE-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-17178. -- Release Note: Fixed configured event listeners resource injection order. Resolution: Fixed LGTM. Merged into the master. [~PetrovMikhail], thank you for the contribution. > Notify preconfigured event listeners about node start after resources were > injected. > > > Key: IGNITE-17178 > URL: https://issues.apache.org/jira/browse/IGNITE-17178 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > We need to notify preconfigured event listeners about node start after > resources were injected. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17136) Update Ignite dependency: Tomcat Servlet API
[ https://issues.apache.org/jira/browse/IGNITE-17136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17136: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: Tomcat Servlet API > > > Key: IGNITE-17136 > URL: https://issues.apache.org/jira/browse/IGNITE-17136 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Minor > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update Tomcat Servlet API dependency 9.0.10 to 9.0.63 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17137) Move ignite-cloud to the Ignite Extensions project
[ https://issues.apache.org/jira/browse/IGNITE-17137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552131#comment-17552131 ] Amelchev Nikita commented on IGNITE-17137: -- [~mmuzaf], LGTM. > Move ignite-cloud to the Ignite Extensions project > -- > > Key: IGNITE-17137 > URL: https://issues.apache.org/jira/browse/IGNITE-17137 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Move ignite-cloud to the Ignite Extensions project -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17140) Snapshot restore: use the snapshot pool to copy transferred partitions.
[ https://issues.apache.org/jira/browse/IGNITE-17140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17140: - Fix Version/s: 2.14 > Snapshot restore: use the snapshot pool to copy transferred partitions. > --- > > Key: IGNITE-17140 > URL: https://issues.apache.org/jira/browse/IGNITE-17140 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.14 > > > For now, TransmissionHandler#fileHandler is used to process transferred > partitions (files move I/O operation). It can cause socket timeout and > restore process stop. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17140) Snapshot restore: use the snapshot pool to copy transferred partitions.
Amelchev Nikita created IGNITE-17140: Summary: Snapshot restore: use the snapshot pool to copy transferred partitions. Key: IGNITE-17140 URL: https://issues.apache.org/jira/browse/IGNITE-17140 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita For now, TransmissionHandler#fileHandler is used to process transferred partitions (files move I/O operation). It can cause socket timeout and restore process stop. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17096) Update Ignite dependency: jsonpath
[ https://issues.apache.org/jira/browse/IGNITE-17096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17096: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: jsonpath > -- > > Key: IGNITE-17096 > URL: https://issues.apache.org/jira/browse/IGNITE-17096 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Minor > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update jsonpath dependency 2.4.0 to 2.7.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17086) SQL: long query warning not printed for lazy queries
[ https://issues.apache.org/jira/browse/IGNITE-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17086: - Attachment: (was: LongQueryWarningTest.java) > SQL: long query warning not printed for lazy queries > > > Key: IGNITE-17086 > URL: https://issues.apache.org/jira/browse/IGNITE-17086 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Priority: Major > Labels: ise > Attachments: LongQueryWarningTest.java > > > Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17086) SQL: long query warning not printed for lazy queries
[ https://issues.apache.org/jira/browse/IGNITE-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17086: - Attachment: LongQueryWarningTest.java > SQL: long query warning not printed for lazy queries > > > Key: IGNITE-17086 > URL: https://issues.apache.org/jira/browse/IGNITE-17086 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Priority: Major > Labels: ise > Attachments: LongQueryWarningTest.java > > > Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17086) SQL: long query warning not printed for lazy queries
[ https://issues.apache.org/jira/browse/IGNITE-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17086: - Labels: ise (was: ) > SQL: long query warning not printed for lazy queries > > > Key: IGNITE-17086 > URL: https://issues.apache.org/jira/browse/IGNITE-17086 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Priority: Major > Labels: ise > Attachments: LongQueryWarningTest.java > > > Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17086) SQL: long query warning not printed for lazy queries
[ https://issues.apache.org/jira/browse/IGNITE-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17086: - Attachment: LongQueryWarningTest.java > SQL: long query warning not printed for lazy queries > > > Key: IGNITE-17086 > URL: https://issues.apache.org/jira/browse/IGNITE-17086 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Priority: Major > Attachments: LongQueryWarningTest.java > > > Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17086) SQL: long query warning not printed for lazy queries
Amelchev Nikita created IGNITE-17086: Summary: SQL: long query warning not printed for lazy queries Key: IGNITE-17086 URL: https://issues.apache.org/jira/browse/IGNITE-17086 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-15067) Add custom destination path to the snapshost API
[
https://issues.apache.org/jira/browse/IGNITE-15067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17545467#comment-17545467
]
Amelchev Nikita commented on IGNITE-15067:
--
[~xtern], LGTM.
> Add custom destination path to the snapshost API
>
>
> Key: IGNITE-15067
> URL: https://issues.apache.org/jira/browse/IGNITE-15067
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The default configuration path obtains from the IgniteConfiguration. However,
> in some circumstances, it is good to set this destination path at runtime.
> This path must be configured relatively in the node working directory and
> must be accessible from the security point of view.
> Proposed API:
> {code}
> public IgniteFuture createSnapshot(String name, String locPath);
> {code}
> control.sh *create* snapshot command syntax
> {noformat}
> control.(sh|bat) --snapshot create snapshot_name [--dest path] [--sync]
> Parameters:
> snapshot_name - Snapshot name.
> path - Path to the directory where the snapshot will be saved. If
> not specified, the default snapshot directory will be used.
> sync - Run the operation synchronously, the command will wait for
> the entire operation to complete. Otherwise, it will be performed in the
> background, and the command will immediately return control.
> {noformat}
> control.sh *check* snapshot command syntax
> {noformat}
> control.(sh|bat) --snapshot check snapshot_name [--src path]
> Parameters:
> snapshot_name - Snapshot name.
> path - Path to the directory where the snapshot files are
> located. If not specified, the default snapshot directory will be used.
> {noformat}
> control.sh *restore* snapshot command syntax
> {noformat}
> control.(sh|bat) --snapshot restore snapshot_name --start [--groups
> group1,...groupN] [--src path] [--sync]
> Parameters:
> snapshot_name - Snapshot name.
> group1,...groupN - Cache group names.
> path - Path to the directory where the snapshot files are
> located. If not specified, the default snapshot directory will be used.
> sync - Run the operation synchronously, the command will wait
> for the entire operation to complete. Otherwise, it will be performed in the
> background, and the command will immediately return control.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator
[
https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita reassigned IGNITE-17051:
Assignee: Mikhail Petrov
> Incorrect parsing of 'IN' clause in IgniteQueryGenerator
>
>
> Key: IGNITE-17051
> URL: https://issues.apache.org/jira/browse/IGNITE-17051
> Project: Ignite
> Issue Type: Bug
> Components: springdata
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: ise
> Attachments: IncorrectInOperator.patch
>
>
> If you create JPA-repository method with with 'IN' operator (eg.
> findBySecondName{*}In{*}), it should be parsed in correct SQL form, but when
> such repository method is called, below error occurs:
> {code:java}
> Syntax error in SQL statement "SELECT ""PersonCache"".""PERSON""._KEY,
> ""PersonCache"".""PERSON""._VAL FROM PERSON WHERE ((PERSON.SECONDNAME IN
> ?[*])) "; expected "("; SQL statement:
> SELECT "PersonCache"."PERSON"._KEY, "PersonCache"."PERSON"._VAL FROM Person
> WHERE ((Person.secondName IN ?)) [42001-197]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:861)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:420)
> at
> org.apache.ignite.springdata.proxy.IgniteNodeCacheProxy.query(IgniteNodeCacheProxy.java:90)
> at
> org.apache.ignite.springdata.repository.query.IgniteRepositoryQuery.execute(IgniteRepositoryQuery.java:348)
> at
> org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.doInvoke(RepositoryFactorySupport.java:619)
> at
> org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.invoke(RepositoryFactorySupport.java:606)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
> at com.sun.proxy.$Proxy51.findBySecondNameIn(Unknown Source)
> at
> org.apache.ignite.springdata.IgniteSpringDataCrudSelfTest.testGetPersonsBySecondNameInList(IgniteSpringDataCrudSelfTest.java:453)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2434)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Here is a reproducer patch (apply to master of ignite-extensions):
> [^IncorrectInOperator.patch]. It contains two tests for single argument and
> for list of arguments.
> It seems, that {{IgniteQueryGenerator}} incorrectly handles {{IN}} (and
> {{{}NOT IN{}}}) operator [1], because if you place '?' between parenthesis,
> error will disappear for single argument.
> But there is another problem after addition of parenthesis: if Collection is
> passed as argument below error will occur:
> {code:java}
> General error: "class org.apache.ignite.IgniteCheckedException: Runtime
> failure on bounds: [lower=IndexSearchRowImpl
> [rowHnd=org.apache.ignite.internal.processors.query.h2.index.QueryIndexRowHandler@6183d0d9],
> upper=IndexSearchRowImpl
> [rowHnd=org.apache.ignite.internal.processors.query.h2.index.QueryIndexRowHandler@6183d0d9]]";
> SQL statement:
> SELECT
> "PersonCache".__Z0._KEY __C0_0,
> "PersonCache".__Z0._VAL __C0_1
> FROM "PersonCache".PERSON __Z0
> WHERE __Z0.SECONDNAME = ?1 [5-197]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:900)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:987)
> at
>
[jira] [Created] (IGNITE-17047) Cleanup GridTestSafeThreadFactory threads after each test
Amelchev Nikita created IGNITE-17047: Summary: Cleanup GridTestSafeThreadFactory threads after each test Key: IGNITE-17047 URL: https://issues.apache.org/jira/browse/IGNITE-17047 Project: Ignite Issue Type: Improvement Reporter: Amelchev Nikita Assignee: Amelchev Nikita The test framework cleans GridTestSafeThreadFactory threads after all tests in class. This leads to hanging the whole test class and a suite timeout. Example of suite timeout: https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache2/6456823?showRootCauses=false=true=true The root cause - nodes can't be stopped after tests due to the test thread blocking node start. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17042) Fix flaky tests failed due to client cache is null
[
https://issues.apache.org/jira/browse/IGNITE-17042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17042:
-
Fix Version/s: 2.14
> Fix flaky tests failed due to client cache is null
> --
>
> Key: IGNITE-17042
> URL: https://issues.apache.org/jira/browse/IGNITE-17042
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.14
>
>
> There are several tests that failed due to client cache is null:
> {noformat}
> grid(0).createCache(ccfg);
> clientCache = client.cache(ccfg.getName());
> clientCache.put(); // Cache can be null due to client registers cache
> asynchroniously.
> {noformat}
> Example of test:
> CacheEntryProcessorNonSerializableTest.testPessimisticFullSync
> {noformat}
> === Failed test run #1 ==
> --- Stdout: ---
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.doTestInvokeTest(CacheEntryProcessorNonSerializableTest.java:437)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.testPessimisticFullSync(CacheEntryProcessorNonSerializableTest.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2434)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17042) Fix flaky tests failed due to client cache is null
Amelchev Nikita created IGNITE-17042:
Summary: Fix flaky tests failed due to client cache is null
Key: IGNITE-17042
URL: https://issues.apache.org/jira/browse/IGNITE-17042
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
There are several tests that failed due to client cache is null:
{noformat}
grid(0).createCache(ccfg);
clientCache = client.cache(ccfg.getName());
clientCache.put(); // Can be null due client registers cache asynchroniously.
{noformat}
Example of test: CacheEntryProcessorNonSerializableTest.testPessimisticFullSync
{noformat}
=== Failed test run #1 ==
--- Stdout: ---
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.doTestInvokeTest(CacheEntryProcessorNonSerializableTest.java:437)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.testPessimisticFullSync(CacheEntryProcessorNonSerializableTest.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2434)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17042) Fix flaky tests failed due to client cache is null
[
https://issues.apache.org/jira/browse/IGNITE-17042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-17042:
-
Description:
There are several tests that failed due to client cache is null:
{noformat}
grid(0).createCache(ccfg);
clientCache = client.cache(ccfg.getName());
clientCache.put(); // Cache can be null due to client registers cache
asynchroniously.
{noformat}
Example of test: CacheEntryProcessorNonSerializableTest.testPessimisticFullSync
{noformat}
=== Failed test run #1 ==
--- Stdout: ---
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.doTestInvokeTest(CacheEntryProcessorNonSerializableTest.java:437)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.testPessimisticFullSync(CacheEntryProcessorNonSerializableTest.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2434)
at java.lang.Thread.run(Thread.java:748)
{noformat}
was:
There are several tests that failed due to client cache is null:
{noformat}
grid(0).createCache(ccfg);
clientCache = client.cache(ccfg.getName());
clientCache.put(); // Can be null due client registers cache asynchroniously.
{noformat}
Example of test: CacheEntryProcessorNonSerializableTest.testPessimisticFullSync
{noformat}
=== Failed test run #1 ==
--- Stdout: ---
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.doTestInvokeTest(CacheEntryProcessorNonSerializableTest.java:437)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.testPessimisticFullSync(CacheEntryProcessorNonSerializableTest.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2434)
at java.lang.Thread.run(Thread.java:748)
{noformat}
> Fix flaky tests failed due to client cache is null
> --
>
> Key: IGNITE-17042
> URL: https://issues.apache.org/jira/browse/IGNITE-17042
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>
> There are several tests that failed due to client cache is null:
> {noformat}
> grid(0).createCache(ccfg);
> clientCache = client.cache(ccfg.getName());
> clientCache.put(); // Cache can be null due to client registers cache
> asynchroniously.
> {noformat}
> Example of test:
> CacheEntryProcessorNonSerializableTest.testPessimisticFullSync
> {noformat}
> === Failed test run #1 ==
> --- Stdout: ---
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.doTestInvokeTest(CacheEntryProcessorNonSerializableTest.java:437)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorNonSerializableTest.testPessimisticFullSync(CacheEntryProcessorNonSerializableTest.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
>
[jira] [Updated] (IGNITE-17039) [Extensions] Fix binary assembly of performance statistics module
[ https://issues.apache.org/jira/browse/IGNITE-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17039: - Component/s: extensions > [Extensions] Fix binary assembly of performance statistics module > - > > Key: IGNITE-17039 > URL: https://issues.apache.org/jira/browse/IGNITE-17039 > Project: Ignite > Issue Type: Bug > Components: extensions >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > > The release build was broken after IGNITE-16847. The release archive does not > include UI resources. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17039) [Extensions] Fix binary assembly of performance statistics module
[ https://issues.apache.org/jira/browse/IGNITE-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542457#comment-17542457 ] Amelchev Nikita commented on IGNITE-17039: -- TC run: https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_PerformanceStatistics/6453935?showRootCauses=false=true > [Extensions] Fix binary assembly of performance statistics module > - > > Key: IGNITE-17039 > URL: https://issues.apache.org/jira/browse/IGNITE-17039 > Project: Ignite > Issue Type: Bug > Components: extensions >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > > The release build was broken after IGNITE-16847. The release archive does not > include UI resources. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17039) [Extensions] Fix binary assembly of performance statistics module
Amelchev Nikita created IGNITE-17039: Summary: [Extensions] Fix binary assembly of performance statistics module Key: IGNITE-17039 URL: https://issues.apache.org/jira/browse/IGNITE-17039 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The release build was broken after IGNITE-16847. The release archive does not include UI resources. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17035) The testChangeSnapshotTransferRateInRuntime test is flaky.
[ https://issues.apache.org/jira/browse/IGNITE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17035: - Fix Version/s: 2.14 > The testChangeSnapshotTransferRateInRuntime test is flaky. > -- > > Key: IGNITE-17035 > URL: https://issues.apache.org/jira/browse/IGNITE-17035 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Minor > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > The test is flaky: > https://ci2.ignite.apache.org/test/5720057658324237232?currentProjectId=IgniteTests24Java8=%3Cdefault%3E=true > The reason - it does not take into account release time of > BasicRateLimiter#acquire() after rate set to unlimited. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17035) The testChangeSnapshotTransferRateInRuntime test is flaky.
[ https://issues.apache.org/jira/browse/IGNITE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17035: - Ignite Flags: (was: Docs Required,Release Notes Required) > The testChangeSnapshotTransferRateInRuntime test is flaky. > -- > > Key: IGNITE-17035 > URL: https://issues.apache.org/jira/browse/IGNITE-17035 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The test is flaky: > https://ci2.ignite.apache.org/test/5720057658324237232?currentProjectId=IgniteTests24Java8=%3Cdefault%3E=true > The reason - it does not take into account release time of > BasicRateLimiter#acquire() after rate set to unlimited. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17035) The testChangeSnapshotTransferRateInRuntime test is flaky.
[ https://issues.apache.org/jira/browse/IGNITE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542383#comment-17542383 ] Amelchev Nikita commented on IGNITE-17035: -- Multiple tests run: https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6453509?showRootCauses=false > The testChangeSnapshotTransferRateInRuntime test is flaky. > -- > > Key: IGNITE-17035 > URL: https://issues.apache.org/jira/browse/IGNITE-17035 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The test is flaky: > https://ci2.ignite.apache.org/test/5720057658324237232?currentProjectId=IgniteTests24Java8=%3Cdefault%3E=true > The reason - it does not take into account release time of > BasicRateLimiter#acquire() after rate set to unlimited. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17035) The testChangeSnapshotTransferRateInRuntime test is flaky.
Amelchev Nikita created IGNITE-17035: Summary: The testChangeSnapshotTransferRateInRuntime test is flaky. Key: IGNITE-17035 URL: https://issues.apache.org/jira/browse/IGNITE-17035 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita The test is flaky: https://ci2.ignite.apache.org/test/5720057658324237232?currentProjectId=IgniteTests24Java8=%3Cdefault%3E=true The reason - it does not take into account release time of BasicRateLimiter#acquire() after rate set to unlimited. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17026) Add the 2.13 version to compatibility tests
[ https://issues.apache.org/jira/browse/IGNITE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17026: - Fix Version/s: 2.14 > Add the 2.13 version to compatibility tests > --- > > Key: IGNITE-17026 > URL: https://issues.apache.org/jira/browse/IGNITE-17026 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Add the 2.13 version to compatibility tests -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17026) Add the 2.13 version to compatibility tests
[ https://issues.apache.org/jira/browse/IGNITE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-17026. -- Resolution: Fixed Merged into the master. [~xtern], thanks for the review. > Add the 2.13 version to compatibility tests > --- > > Key: IGNITE-17026 > URL: https://issues.apache.org/jira/browse/IGNITE-17026 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add the 2.13 version to compatibility tests -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16888) Update Ignite dependency: lz4
[ https://issues.apache.org/jira/browse/IGNITE-16888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16888: - Fix Version/s: 2.14 > Update Ignite dependency: lz4 > - > > Key: IGNITE-16888 > URL: https://issues.apache.org/jira/browse/IGNITE-16888 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update lz4 dependency 1.5.0 to 1.8.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17026) Add the 2.13 version to compatibility tests
[ https://issues.apache.org/jira/browse/IGNITE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita reassigned IGNITE-17026: Assignee: Amelchev Nikita > Add the 2.13 version to compatibility tests > --- > > Key: IGNITE-17026 > URL: https://issues.apache.org/jira/browse/IGNITE-17026 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add the 2.13 version to compatibility tests -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17026) Add the 2.13 version to compatibility tests
Amelchev Nikita created IGNITE-17026: Summary: Add the 2.13 version to compatibility tests Key: IGNITE-17026 URL: https://issues.apache.org/jira/browse/IGNITE-17026 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Add the 2.13 version to compatibility tests -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17005) Implement metrics for a snapshot create operation
[ https://issues.apache.org/jira/browse/IGNITE-17005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17005: - Fix Version/s: 2.14 > Implement metrics for a snapshot create operation > - > > Key: IGNITE-17005 > URL: https://issues.apache.org/jira/browse/IGNITE-17005 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.14 > > > Snapshot create operation can take a long time, we must be able to track its > progress using metrics. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17005) Implement metrics for a snapshot create operation
[ https://issues.apache.org/jira/browse/IGNITE-17005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17005: - Labels: ise (was: ) > Implement metrics for a snapshot create operation > - > > Key: IGNITE-17005 > URL: https://issues.apache.org/jira/browse/IGNITE-17005 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: ise > Fix For: 2.14 > > > Snapshot create operation can take a long time, we must be able to track its > progress using metrics. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17005) Implement metrics for a snapshot create operation
Amelchev Nikita created IGNITE-17005: Summary: Implement metrics for a snapshot create operation Key: IGNITE-17005 URL: https://issues.apache.org/jira/browse/IGNITE-17005 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Snapshot create operation can take a long time, we must be able to track its progress using metrics. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-12502) Document ignite-spring-data_2.2 module
[ https://issues.apache.org/jira/browse/IGNITE-12502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-12502. -- Resolution: Won't Fix The module was documented: https://ignite.apache.org/docs/latest/extensions-and-integrations/spring/spring-data > Document ignite-spring-data_2.2 module > -- > > Key: IGNITE-12502 > URL: https://issues.apache.org/jira/browse/IGNITE-12502 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Priority: Major > > After IGNITE-12259 > I think there are no API changes, but we should mention that we have such > module and what its dependencies are. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16239) [Extensions] Document the zookeeper-ip-finder-ext extension.
[ https://issues.apache.org/jira/browse/IGNITE-16239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16239: - Fix Version/s: 2.13 > [Extensions] Document the zookeeper-ip-finder-ext extension. > > > Key: IGNITE-16239 > URL: https://issues.apache.org/jira/browse/IGNITE-16239 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Priority: Minor > Fix For: 2.13 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16895) Update documentation with GitHub Actions
[ https://issues.apache.org/jira/browse/IGNITE-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532282#comment-17532282 ] Amelchev Nikita edited comment on IGNITE-16895 at 5/5/22 2:48 PM: -- Merged into the master. [~mmuzaf], thank you for the review! was (Author: nsamelchev): Merged into the master. > Update documentation with GitHub Actions > > > Key: IGNITE-16895 > URL: https://issues.apache.org/jira/browse/IGNITE-16895 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > GitHub Actions can be used to update documentation for released Ignite > versions. > For now, this is a complex manual work that requires understanding all the > intermediate steps: > [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. > I propose to automatize this and give an ability to update documentation on a > push event to a released branch. > ASF GitHub Actions Policy allows automated services to push changes related > to documentation: > [policy|https://infra.apache.org/github-actions-policy.html]. > Write access is > [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] > to run the update. So, only committers can run workflows manually. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16895) Update documentation with GitHub Actions
[ https://issues.apache.org/jira/browse/IGNITE-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16895: - Description: GitHub Actions can be used to update documentation for released Ignite versions. For now, this is a complex manual work that requires understanding all the intermediate steps: [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. I propose to automatize this and give an ability to update documentation on a push event to a released branch. ASF GitHub Actions Policy allows automated services to push changes related to documentation: [policy|https://infra.apache.org/github-actions-policy.html]. Write access is [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] to run the update. So, only committers can run workflows manually. was: GitHub Actions can be used to update documentation for released Ignite versions. For now, this is a complex manual work that requires understanding all the intermediate steps: [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. I propose to automatize this and give an ability to update documentation by a click (or on a push to a released branch event): ASF GitHub Actions Policy allows automated services to push changes related to documentation: [policy|https://infra.apache.org/github-actions-policy.html]. Write access is [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] to run the update. So, only committers can run workflows manually. > Update documentation with GitHub Actions > > > Key: IGNITE-16895 > URL: https://issues.apache.org/jira/browse/IGNITE-16895 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > GitHub Actions can be used to update documentation for released Ignite > versions. > For now, this is a complex manual work that requires understanding all the > intermediate steps: > [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. > I propose to automatize this and give an ability to update documentation on a > push event to a released branch. > ASF GitHub Actions Policy allows automated services to push changes related > to documentation: > [policy|https://infra.apache.org/github-actions-policy.html]. > Write access is > [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] > to run the update. So, only committers can run workflows manually. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16895) Update documentation with GitHub Actions
[ https://issues.apache.org/jira/browse/IGNITE-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16895: - Attachment: (was: image-2022-04-23-16-19-41-327.png) > Update documentation with GitHub Actions > > > Key: IGNITE-16895 > URL: https://issues.apache.org/jira/browse/IGNITE-16895 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > GitHub Actions can be used to update documentation for released Ignite > versions. > For now, this is a complex manual work that requires understanding all the > intermediate steps: > [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. > I propose to automatize this and give an ability to update documentation on a > push event to a released branch. > ASF GitHub Actions Policy allows automated services to push changes related > to documentation: > [policy|https://infra.apache.org/github-actions-policy.html]. > Write access is > [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] > to run the update. So, only committers can run workflows manually. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16895) Update documentation with GitHub Actions
[ https://issues.apache.org/jira/browse/IGNITE-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16895: - Description: GitHub Actions can be used to update documentation for released Ignite versions. For now, this is a complex manual work that requires understanding all the intermediate steps: [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. I propose to automatize this and give an ability to update documentation by a click (or on a push to a released branch event): ASF GitHub Actions Policy allows automated services to push changes related to documentation: [policy|https://infra.apache.org/github-actions-policy.html]. Write access is [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] to run the update. So, only committers can run workflows manually. was: GitHub Actions can be used to update documentation for released Ignite versions. For now, this is a complex manual work that requires understanding all the intermediate steps: [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. I propose to automatize this and give an ability to update documentation by a click (or on a push to a released branch event): !image-2022-04-23-16-19-41-327.png|width=260,height=216! ASF GitHub Actions Policy allows automated services to push changes related to documentation: [policy|https://infra.apache.org/github-actions-policy.html]. Write access is [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] to run the update. So, only committers can run workflows manually. > Update documentation with GitHub Actions > > > Key: IGNITE-16895 > URL: https://issues.apache.org/jira/browse/IGNITE-16895 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Attachments: image-2022-04-23-16-19-41-327.png > > Time Spent: 10m > Remaining Estimate: 0h > > GitHub Actions can be used to update documentation for released Ignite > versions. > For now, this is a complex manual work that requires understanding all the > intermediate steps: > [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs]. > I propose to automatize this and give an ability to update documentation by a > click (or on a push to a released branch event): > ASF GitHub Actions Policy allows automated services to push changes related > to documentation: > [policy|https://infra.apache.org/github-actions-policy.html]. > Write access is > [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] > to run the update. So, only committers can run workflows manually. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16904) Release Apache Ignite 2.13
[ https://issues.apache.org/jira/browse/IGNITE-16904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530348#comment-17530348 ] Amelchev Nikita commented on IGNITE-16904: -- [~nsafonov], Thank you! > Release Apache Ignite 2.13 > -- > > Key: IGNITE-16904 > URL: https://issues.apache.org/jira/browse/IGNITE-16904 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
