[jira] [Assigned] (IGNITE-21830) Add logging of connection check for each address
[ https://issues.apache.org/jira/browse/IGNITE-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-21830: --- Assignee: Maksim Davydov (was: Luchnikov Alexander) > Add logging of connection check for each address > > > Key: IGNITE-21830 > URL: https://issues.apache.org/jira/browse/IGNITE-21830 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > > Currently, exception thrown during checking of address is ignored [1]. It > would be useful to print message with connection check summary including each > address checking state and error message (if any). > # > https://github.com/apache/ignite/blob/7cd0c7a7d1150bbf6be6aae5efe80627a73757c0/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L7293 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21830) Add logging of connection check for each address
[ https://issues.apache.org/jira/browse/IGNITE-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840454#comment-17840454 ] Maksim Davydov commented on IGNITE-21830: - PR url: https://github.com/apache/ignite/pull/11327 > Add logging of connection check for each address > > > Key: IGNITE-21830 > URL: https://issues.apache.org/jira/browse/IGNITE-21830 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > Time Spent: 10m > Remaining Estimate: 0h > > Currently, exception thrown during checking of address is ignored [1]. It > would be useful to print message with connection check summary including each > address checking state and error message (if any). > # > https://github.com/apache/ignite/blob/7cd0c7a7d1150bbf6be6aae5efe80627a73757c0/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L7293 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-21830) Add logging of connection check for each address
[ https://issues.apache.org/jira/browse/IGNITE-21830 ] Maksim Davydov deleted comment on IGNITE-21830: - was (Author: JIRAUSER305006): PR url: https://github.com/apache/ignite/pull/11327 > Add logging of connection check for each address > > > Key: IGNITE-21830 > URL: https://issues.apache.org/jira/browse/IGNITE-21830 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > Time Spent: 10m > Remaining Estimate: 0h > > Currently, exception thrown during checking of address is ignored [1]. It > would be useful to print message with connection check summary including each > address checking state and error message (if any). > # > https://github.com/apache/ignite/blob/7cd0c7a7d1150bbf6be6aae5efe80627a73757c0/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L7293 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22189) Display Expiry Policy information in the system view
Maksim Davydov created IGNITE-22189:
---
Summary: Display Expiry Policy information in the system view
Key: IGNITE-22189
URL: https://issues.apache.org/jira/browse/IGNITE-22189
Project: Ignite
Issue Type: Improvement
Reporter: Maksim Davydov
Assignee: Maksim Davydov
The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
string representation, which at this point is a simple className +@ + hashCode
in hex, that is default {{Object#toString()}} behaviour. This is not
informative for an end user of the API.
In addition, it is useful to have information about existing cache entries that
are about to expire (eligible for cache expiry policy).
{*}TODO{*}:
* To make the {{CacheView#expiryPolicyFactory}} method return readable,
human-oriented output, one should refactor the method or
{{Factory}} child classes to provide the cache expiry policy
setting in readable form with policy type and ttl.
* Within the cache group view ({{CacheGroupView}}), check the entries presence
eligible for expiry policy. It can be done with O(1) time complexity for
in-memory, and O(number of partitions) for persistent mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22189) Display Expiry Policy information in the system view
[
https://issues.apache.org/jira/browse/IGNITE-22189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov updated IGNITE-22189:
Description:
The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
string representation, which at this point is a simple className +@ + hashCode
in hex, that is default {{Object#toString()}} behaviour. This is not
informative for an end user of the API.
In addition, it is useful to have information about existing cache entries that
are about to expire (eligible for cache expiry policy).
{*}TODO{*}:
* To make the {{CacheView#expiryPolicyFactory}} method return readable,
human-oriented output, one should refactor the method or
{{Factory}} child classes to provide the cache expiry policy
setting in readable form with policy type and ttl.
* Within the cache group view ({{{}CacheGroupView{}}}), check the entries
presence eligible for expiry policy. It can be done with O(1) time complexity
for in-memory, and O(number of partitions) for persistent mode.
* Within the cache view ({{{}CacheView{}}}), check the entries presence
eligible for expiry policy. It can be done with O(logN) time complexity for
in-memory, and O(number of partitions) for persistent mode.
was:
The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
string representation, which at this point is a simple className +@ + hashCode
in hex, that is default {{Object#toString()}} behaviour. This is not
informative for an end user of the API.
In addition, it is useful to have information about existing cache entries that
are about to expire (eligible for cache expiry policy).
{*}TODO{*}:
* To make the {{CacheView#expiryPolicyFactory}} method return readable,
human-oriented output, one should refactor the method or
{{Factory}} child classes to provide the cache expiry policy
setting in readable form with policy type and ttl.
* Within the cache group view ({{CacheGroupView}}), check the entries presence
eligible for expiry policy. It can be done with O(1) time complexity for
in-memory, and O(number of partitions) for persistent mode.
> Display Expiry Policy information in the system view
>
>
> Key: IGNITE-22189
> URL: https://issues.apache.org/jira/browse/IGNITE-22189
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maksim Davydov
>Assignee: Maksim Davydov
>Priority: Minor
> Labels: ise
>
> The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
> string representation, which at this point is a simple className +@ +
> hashCode in hex, that is default {{Object#toString()}} behaviour. This is not
> informative for an end user of the API.
> In addition, it is useful to have information about existing cache entries
> that are about to expire (eligible for cache expiry policy).
> {*}TODO{*}:
> * To make the {{CacheView#expiryPolicyFactory}} method return readable,
> human-oriented output, one should refactor the method or
> {{Factory}} child classes to provide the cache expiry policy
> setting in readable form with policy type and ttl.
> * Within the cache group view ({{{}CacheGroupView{}}}), check the entries
> presence eligible for expiry policy. It can be done with O(1) time complexity
> for in-memory, and O(number of partitions) for persistent mode.
> * Within the cache view ({{{}CacheView{}}}), check the entries presence
> eligible for expiry policy. It can be done with O(logN) time complexity for
> in-memory, and O(number of partitions) for persistent mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18372) Add CDC metrics to KafkaToIgniteStreamer
[
https://issues.apache.org/jira/browse/IGNITE-18372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov reassigned IGNITE-18372:
---
Assignee: Maksim Davydov
> Add CDC metrics to KafkaToIgniteStreamer
>
>
> Key: IGNITE-18372
> URL: https://issues.apache.org/jira/browse/IGNITE-18372
> Project: Ignite
> Issue Type: New Feature
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Maksim Davydov
>Priority: Major
> Labels: IEP-59, ise
>
> We need metrics for received events count and last received event timestamp
> for the {{KafkaToIgniteStreamer}}, because there can be situations, when
> events sent by {{IgniteToKafkaStreamer}} are lost in Kafka due to Kafka
> failures or topic's retention configuration.
> In such situations we should be able to compare to sent messages count on
> source cluster with received messages count on destination one. Timestamp of
> last received event would be also useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22189) Display Expiry Policy information in the system view
[
https://issues.apache.org/jira/browse/IGNITE-22189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov updated IGNITE-22189:
Description:
The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
string representation, which at this point is a simple className +@ + hashCode
in hex, that is default {{Object#toString()}} behaviour. This is not
informative for an end user of the API.
In addition, it is useful to have information about existing cache entries that
are about to expire (eligible for cache expiry policy).
{*}TODO{*}:
* To make the {{CacheView#expiryPolicyFactory}} method return readable,
human-oriented output, one should refactor the method or
{{Factory}} child classes to provide the cache expiry policy
setting in readable form with policy type and ttl.
* Within the cache view ({{{}CacheView{}}}), check the entries presence
eligible for expiry policy. It can be done with O(logN) time complexity for
in-memory, and O(number of partitions) for persistent mode.
was:
The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
string representation, which at this point is a simple className +@ + hashCode
in hex, that is default {{Object#toString()}} behaviour. This is not
informative for an end user of the API.
In addition, it is useful to have information about existing cache entries that
are about to expire (eligible for cache expiry policy).
{*}TODO{*}:
* To make the {{CacheView#expiryPolicyFactory}} method return readable,
human-oriented output, one should refactor the method or
{{Factory}} child classes to provide the cache expiry policy
setting in readable form with policy type and ttl.
* Within the cache group view ({{{}CacheGroupView{}}}), check the entries
presence eligible for expiry policy. It can be done with O(1) time complexity
for in-memory, and O(number of partitions) for persistent mode.
* Within the cache view ({{{}CacheView{}}}), check the entries presence
eligible for expiry policy. It can be done with O(logN) time complexity for
in-memory, and O(number of partitions) for persistent mode.
> Display Expiry Policy information in the system view
>
>
> Key: IGNITE-22189
> URL: https://issues.apache.org/jira/browse/IGNITE-22189
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maksim Davydov
>Assignee: Maksim Davydov
>Priority: Minor
> Labels: ise
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
> string representation, which at this point is a simple className +@ +
> hashCode in hex, that is default {{Object#toString()}} behaviour. This is not
> informative for an end user of the API.
> In addition, it is useful to have information about existing cache entries
> that are about to expire (eligible for cache expiry policy).
> {*}TODO{*}:
> * To make the {{CacheView#expiryPolicyFactory}} method return readable,
> human-oriented output, one should refactor the method or
> {{Factory}} child classes to provide the cache expiry policy
> setting in readable form with policy type and ttl.
> * Within the cache view ({{{}CacheView{}}}), check the entries presence
> eligible for expiry policy. It can be done with O(logN) time complexity for
> in-memory, and O(number of partitions) for persistent mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22403) Algorithm improvement for kafka topic partition distribution
Maksim Davydov created IGNITE-22403: --- Summary: Algorithm improvement for kafka topic partition distribution Key: IGNITE-22403 URL: https://issues.apache.org/jira/browse/IGNITE-22403 Project: Ignite Issue Type: Improvement Components: extensions Reporter: Maksim Davydov Assignee: Maksim Davydov Distribution for partitions from kafka topic over requested threads in AbstractKafkaToIgniteCdcStreamer (CDC Kafka to Ignite) is not uniform. There might be cases with unequal load on threads, that reads data from kafka, which might result in overhead/bottleneck and slow workflow in general for the whole CDC with Kafka process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22403) Algorithm improvement for kafka topic partition distribution
[ https://issues.apache.org/jira/browse/IGNITE-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22403: Priority: Major (was: Minor) > Algorithm improvement for kafka topic partition distribution > > > Key: IGNITE-22403 > URL: https://issues.apache.org/jira/browse/IGNITE-22403 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > > Distribution for partitions from kafka topic over requested threads in > AbstractKafkaToIgniteCdcStreamer (CDC Kafka to Ignite) is not uniform. > There might be cases with unequal load on threads, that reads data from > kafka, which might result in overhead/bottleneck and slow workflow in general > for the whole CDC with Kafka process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22403) Algorithm improvement for kafka topic partition distribution
[ https://issues.apache.org/jira/browse/IGNITE-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852832#comment-17852832 ] Maksim Davydov commented on IGNITE-22403: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7902745?buildTab=overview&hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildChangesSection=true&expandBuildDeploymentsSection=false > Algorithm improvement for kafka topic partition distribution > > > Key: IGNITE-22403 > URL: https://issues.apache.org/jira/browse/IGNITE-22403 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > > Distribution for partitions from kafka topic over requested threads in > AbstractKafkaToIgniteCdcStreamer (CDC Kafka to Ignite) is not uniform. > There might be cases with unequal load on threads, that reads data from > kafka, which might result in overhead/bottleneck and slow workflow in general > for the whole CDC with Kafka process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22189) Display Expiry Policy information in the system view
[
https://issues.apache.org/jira/browse/IGNITE-22189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov updated IGNITE-22189:
Ignite Flags: Docs Required
> Display Expiry Policy information in the system view
>
>
> Key: IGNITE-22189
> URL: https://issues.apache.org/jira/browse/IGNITE-22189
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maksim Davydov
>Assignee: Maksim Davydov
>Priority: Minor
> Labels: ise
> Time Spent: 6h
> Remaining Estimate: 0h
>
> The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
> string representation, which at this point is a simple className +@ +
> hashCode in hex, that is default {{Object#toString()}} behaviour. This is not
> informative for an end user of the API.
> In addition, it is useful to have information about existing cache entries
> that are about to expire (eligible for cache expiry policy).
> {*}TODO{*}:
> * To make the {{CacheView#expiryPolicyFactory}} method return readable,
> human-oriented output, one should refactor the method or
> {{Factory}} child classes to provide the cache expiry policy
> setting in readable form with policy type and ttl.
> * Within the cache view ({{{}CacheView{}}}), check the entries presence
> eligible for expiry policy. It can be done with O(logN) time complexity for
> in-memory, and O(number of partitions) for persistent mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22449) Expiry Policy information in the system view documentation
Maksim Davydov created IGNITE-22449: --- Summary: Expiry Policy information in the system view documentation Key: IGNITE-22449 URL: https://issues.apache.org/jira/browse/IGNITE-22449 Project: Ignite Issue Type: Task Components: documentation Reporter: Maksim Davydov Assignee: Maksim Davydov The documetation should be added for Cache View new column *HAS_EXPIRING_ENTRIES* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22536) CDC metrics for rejected entries by conflict resolver
Maksim Davydov created IGNITE-22536: --- Summary: CDC metrics for rejected entries by conflict resolver Key: IGNITE-22536 URL: https://issues.apache.org/jira/browse/IGNITE-22536 Project: Ignite Issue Type: Task Components: extensions Reporter: Maksim Davydov Assignee: Maksim Davydov The metric is needed for to track the number of entries rejected by conflict resolver during CDC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22536) CDC metrics for rejected entries by conflict resolver
[ https://issues.apache.org/jira/browse/IGNITE-22536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22536: Issue Type: New Feature (was: Task) > CDC metrics for rejected entries by conflict resolver > - > > Key: IGNITE-22536 > URL: https://issues.apache.org/jira/browse/IGNITE-22536 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > > The metric is needed for to track the number of entries rejected by conflict > resolver during CDC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22536) CDC metrics for rejected entries by conflict resolver
[ https://issues.apache.org/jira/browse/IGNITE-22536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863071#comment-17863071 ] Maksim Davydov commented on IGNITE-22536: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7948184?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildChangesSection=true > CDC metrics for rejected entries by conflict resolver > - > > Key: IGNITE-22536 > URL: https://issues.apache.org/jira/browse/IGNITE-22536 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > Time Spent: 20m > Remaining Estimate: 0h > > The metric is needed for to track the number of entries rejected by conflict > resolver during CDC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22670) Test cases update for KafkaToIgniteLoaderTest
Maksim Davydov created IGNITE-22670: --- Summary: Test cases update for KafkaToIgniteLoaderTest Key: IGNITE-22670 URL: https://issues.apache.org/jira/browse/IGNITE-22670 Project: Ignite Issue Type: Test Components: extensions Reporter: Maksim Davydov Assignee: Maksim Davydov KafkaToIgniteLoaderTest doesn't cover all possible errors in KafkaToIgniteCdcStreamerConfiguration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22403) CDC: Improve Kafka partition ranges assignment for appliers
[ https://issues.apache.org/jira/browse/IGNITE-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22403: Summary: CDC: Improve Kafka partition ranges assignment for appliers (was: Algorithm improvement for kafka topic partition distribution) > CDC: Improve Kafka partition ranges assignment for appliers > --- > > Key: IGNITE-22403 > URL: https://issues.apache.org/jira/browse/IGNITE-22403 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > > Distribution for partitions from kafka topic over requested threads in > AbstractKafkaToIgniteCdcStreamer (CDC Kafka to Ignite) is not uniform. > There might be cases with unequal load on threads, that reads data from > kafka, which might result in overhead/bottleneck and slow workflow in general > for the whole CDC with Kafka process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-22403) CDC: Improve Kafka partition ranges assignment for appliers
[ https://issues.apache.org/jira/browse/IGNITE-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852832#comment-17852832 ] Maksim Davydov edited comment on IGNITE-22403 at 7/8/24 1:47 PM: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7955206?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildChangesSection=true was (Author: JIRAUSER305006): https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7902745?buildTab=overview&hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildChangesSection=true&expandBuildDeploymentsSection=false > CDC: Improve Kafka partition ranges assignment for appliers > --- > > Key: IGNITE-22403 > URL: https://issues.apache.org/jira/browse/IGNITE-22403 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > > Distribution for partitions from kafka topic over requested threads in > AbstractKafkaToIgniteCdcStreamer (CDC Kafka to Ignite) is not uniform. > There might be cases with unequal load on threads, that reads data from > kafka, which might result in overhead/bottleneck and slow workflow in general > for the whole CDC with Kafka process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-22403) CDC: Improve Kafka partition ranges assignment for appliers
[ https://issues.apache.org/jira/browse/IGNITE-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852832#comment-17852832 ] Maksim Davydov edited comment on IGNITE-22403 at 7/8/24 3:07 PM: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7975276?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildChangesSection=true was (Author: JIRAUSER305006): https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7955206?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildChangesSection=true > CDC: Improve Kafka partition ranges assignment for appliers > --- > > Key: IGNITE-22403 > URL: https://issues.apache.org/jira/browse/IGNITE-22403 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > > Distribution for partitions from kafka topic over requested threads in > AbstractKafkaToIgniteCdcStreamer (CDC Kafka to Ignite) is not uniform. > There might be cases with unequal load on threads, that reads data from > kafka, which might result in overhead/bottleneck and slow workflow in general > for the whole CDC with Kafka process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22403) CDC: Improve Kafka partition ranges assignment for appliers
[ https://issues.apache.org/jira/browse/IGNITE-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864080#comment-17864080 ] Maksim Davydov commented on IGNITE-22403: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7975381?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildChangesSection=true > CDC: Improve Kafka partition ranges assignment for appliers > --- > > Key: IGNITE-22403 > URL: https://issues.apache.org/jira/browse/IGNITE-22403 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > > Distribution for partitions from kafka topic over requested threads in > AbstractKafkaToIgniteCdcStreamer (CDC Kafka to Ignite) is not uniform. > There might be cases with unequal load on threads, that reads data from > kafka, which might result in overhead/bottleneck and slow workflow in general > for the whole CDC with Kafka process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22670) Test cases update for KafkaToIgniteLoaderTest
[ https://issues.apache.org/jira/browse/IGNITE-22670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864702#comment-17864702 ] Maksim Davydov commented on IGNITE-22670: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7954843?expandBuildDeploymentsSection=false&hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildChangesSection=true > Test cases update for KafkaToIgniteLoaderTest > - > > Key: IGNITE-22670 > URL: https://issues.apache.org/jira/browse/IGNITE-22670 > Project: Ignite > Issue Type: Test > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Trivial > Labels: IEP-59, ise > > KafkaToIgniteLoaderTest doesn't cover all possible errors in > KafkaToIgniteCdcStreamerConfiguration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22844) control.sh --consistency repair permissions fixed
Maksim Davydov created IGNITE-22844: --- Summary: control.sh --consistency repair permissions fixed Key: IGNITE-22844 URL: https://issues.apache.org/jira/browse/IGNITE-22844 Project: Ignite Issue Type: Improvement Reporter: Maksim Davydov Assignee: Maksim Davydov Fix For: 2.17 Currently 'Read Repair' task performed for the chosen partitions by control.sh requires additional CACHE_READ and CACHE WRITE permissions in addition to ADMIN_OPS. This is not convinient, as it obliges users to have this additional permissions, when it's not always neccesary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22844) control.sh --consistency repair permissions fixes
[ https://issues.apache.org/jira/browse/IGNITE-22844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22844: Summary: control.sh --consistency repair permissions fixes (was: control.sh --consistency repair permissions fixed) > control.sh --consistency repair permissions fixes > - > > Key: IGNITE-22844 > URL: https://issues.apache.org/jira/browse/IGNITE-22844 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Fix For: 2.17 > > > Currently 'Read Repair' task performed for the chosen partitions by > control.sh requires additional CACHE_READ and CACHE WRITE permissions in > addition to ADMIN_OPS. > This is not convinient, as it obliges users to have this additional > permissions, when it's not always neccesary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22844) control.sh --consistency repair permissions fixes
[ https://issues.apache.org/jira/browse/IGNITE-22844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22844: Description: Currently 'Read Repair' task performed for the chosen partitions by control.sh requires additional CACHE_READ and CACHE PUT permissions in addition to ADMIN_OPS. This is not convinient, as it obliges users to have this additional permissions, when it's not always neccesary. was: Currently 'Read Repair' task performed for the chosen partitions by control.sh requires additional CACHE_READ and CACHE WRITE permissions in addition to ADMIN_OPS. This is not convinient, as it obliges users to have this additional permissions, when it's not always neccesary. > control.sh --consistency repair permissions fixes > - > > Key: IGNITE-22844 > URL: https://issues.apache.org/jira/browse/IGNITE-22844 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently 'Read Repair' task performed for the chosen partitions by > control.sh requires additional CACHE_READ and CACHE PUT permissions in > addition to ADMIN_OPS. > This is not convinient, as it obliges users to have this additional > permissions, when it's not always neccesary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22864) Cache create command: ignore flag and improved output
Maksim Davydov created IGNITE-22864: --- Summary: Cache create command: ignore flag and improved output Key: IGNITE-22864 URL: https://issues.apache.org/jira/browse/IGNITE-22864 Project: Ignite Issue Type: Improvement Reporter: Maksim Davydov Assignee: Maksim Davydov Fix For: 2.17 There are some minor improvements for `control.sh --cache create` command: * Output with created caches * Ignore flag for existing caches -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22862) Add address information to ClientConnectionException stacktrace
[
https://issues.apache.org/jira/browse/IGNITE-22862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov reassigned IGNITE-22862:
---
Assignee: Maksim Davydov
> Add address information to ClientConnectionException stacktrace
> ---
>
> Key: IGNITE-22862
> URL: https://issues.apache.org/jira/browse/IGNITE-22862
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Maksim Davydov
>Priority: Minor
> Labels: ise, newbie
>
> It will be useful to find out from stacktrace which address connection causes
> error. Currently, stacktrace does not have address information:
> {code}
> org.apache.ignite.client.ClientConnectionException: Connection refused
> at
> org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:197)
> at
> org.apache.ignite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:208)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.getOrCreateChannel(ReliableChannel.java:1055)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.getOrCreateChannel(ReliableChannel.java:1033)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.applyOnDefaultChannel(ReliableChannel.java:837)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.channelsInit(ReliableChannel.java:749)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.channelsInit(ReliableChannel.java:733)
> at
> org.apache.ignite.internal.client.thin.TcpIgniteClient.(TcpIgniteClient.java:155)
> at
> org.apache.ignite.internal.client.thin.TcpIgniteClient.(TcpIgniteClient.java:127)
> at
> org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:442)
> at org.apache.ignite.Ignition.startClient(Ignition.java:587)
> at
> org.apache.ignite.examples.client.ClientPutGetExample.main(ClientPutGetExample.java:45)
> Caused by: org.apache.ignite.client.ClientConnectionException: Connection
> refused
> at
> org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:172)
> ... 11 more
> Caused by: java.net.ConnectException: Connection refused
> at java.base/sun.nio.ch.Net.connect0(Native Method)
> at java.base/sun.nio.ch.Net.connect(Net.java:483)
> at java.base/sun.nio.ch.Net.connect(Net.java:472)
> at
> java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:692)
> at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:100)
> at
> org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:152)
> ... 11 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21927) Removal of transactional code in JDBC classes
[ https://issues.apache.org/jira/browse/IGNITE-21927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-21927: --- Assignee: Maksim Davydov > Removal of transactional code in JDBC classes > - > > Key: IGNITE-21927 > URL: https://issues.apache.org/jira/browse/IGNITE-21927 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > > Classes to remove > # NestedTxMode > # Remove txAllowed flag in JdbcConnection > JDBC code must be complaint with a scpecification (see IGNITE-5339). Changes > must provide full compatibility with older versions of servers and clients. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22844) control.sh --consistency repair permissions fixes
[ https://issues.apache.org/jira/browse/IGNITE-22844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22844: Description: Currently 'Read Repair' task performed for the chosen partitions by control.sh requires CACHE_READ and CACHE PUT permissions in addition to ADMIN_OPS. Thus, to perform the comand `control.sh --consistency repair` the one needs all 3 permissions. There is no point to have additional CACHE_READ and CACHE_PUT permissions to perform the operation, as they are useless for the task itself, and introduces security risk, by allowing the user to manipulate the cache in parallel. The solution would be to substitute user's security context with the context of the cluster node that performs the command. The former is used for the ADMIN_OPS permission check and the latter is used for cache. This will ease the requirement for the users to perform `control.sh --consistency repair` without introducing any additional security risk. was: Currently 'Read Repair' task performed for the chosen partitions by control.sh requires additional CACHE_READ and CACHE PUT permissions in addition to ADMIN_OPS. This is not convinient, as it obliges users to have this additional permissions, when it's not always neccesary. > control.sh --consistency repair permissions fixes > - > > Key: IGNITE-22844 > URL: https://issues.apache.org/jira/browse/IGNITE-22844 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently 'Read Repair' task performed for the chosen partitions by > control.sh requires CACHE_READ and CACHE PUT permissions in addition to > ADMIN_OPS. Thus, to perform the comand `control.sh --consistency repair` the > one needs all 3 permissions. > There is no point to have additional CACHE_READ and CACHE_PUT permissions to > perform the operation, as they are useless for the task itself, and > introduces security risk, by allowing the user to manipulate the cache in > parallel. > The solution would be to substitute user's security context with the context > of the cluster node that performs the command. The former is used for the > ADMIN_OPS permission check and the latter is used for cache. This will ease > the requirement for the users to perform `control.sh --consistency repair` > without introducing any additional security risk. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22962) Conflict resolver metrics per cache
Maksim Davydov created IGNITE-22962: --- Summary: Conflict resolver metrics per cache Key: IGNITE-22962 URL: https://issues.apache.org/jira/browse/IGNITE-22962 Project: Ignite Issue Type: New Feature Reporter: Maksim Davydov Assignee: Maksim Davydov Fix For: 2.17 Currently there is no metrics for conflict resolved entries. Thus, it's hard to analyze the overall picture for the process, especially if custom plugin for Conflict Resolver is used. This ticket solves the issue by adding metrics counting for conflict resolver without depending on its origin. Metrics would be accessable for each cache, that is `per cache monitoring`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22962) Conflict resolver metrics per cache
[ https://issues.apache.org/jira/browse/IGNITE-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22962: Component/s: extensions > Conflict resolver metrics per cache > --- > > Key: IGNITE-22962 > URL: https://issues.apache.org/jira/browse/IGNITE-22962 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently there is no metrics for conflict resolved entries. Thus, it's hard > to analyze the overall picture for the process, especially if custom plugin > for Conflict Resolver is used. > This ticket solves the issue by adding metrics counting for conflict resolver > without depending on its origin. Metrics would be accessable for each cache, > that is `per cache monitoring`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22962) Conflict resolver metrics per cache
[ https://issues.apache.org/jira/browse/IGNITE-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-22962: Labels: IEP-59 ise (was: ise) > Conflict resolver metrics per cache > --- > > Key: IGNITE-22962 > URL: https://issues.apache.org/jira/browse/IGNITE-22962 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently there is no metrics for conflict resolved entries. Thus, it's hard > to analyze the overall picture for the process, especially if custom plugin > for Conflict Resolver is used. > This ticket solves the issue by adding metrics counting for conflict resolver > without depending on its origin. Metrics would be accessable for each cache, > that is `per cache monitoring`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22962) Conflict resolver metrics per cache
[ https://issues.apache.org/jira/browse/IGNITE-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872815#comment-17872815 ] Maksim Davydov commented on IGNITE-22962: - CDC exctensions redundant code removal. Test rests: https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/8022449?hideTestsFromDependencies=false&expandBuildChangesSection=true&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false > Conflict resolver metrics per cache > --- > > Key: IGNITE-22962 > URL: https://issues.apache.org/jira/browse/IGNITE-22962 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-59, ise > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently there is no metrics for conflict resolved entries. Thus, it's hard > to analyze the overall picture for the process, especially if custom plugin > for Conflict Resolver is used. > This ticket solves the issue by adding metrics counting for conflict resolver > without depending on its origin. Metrics would be accessable for each cache, > that is `per cache monitoring`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19528) Add examples for CDC
[ https://issues.apache.org/jira/browse/IGNITE-19528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-19528: --- Assignee: Maksim Davydov > Add examples for CDC > > > Key: IGNITE-19528 > URL: https://issues.apache.org/jira/browse/IGNITE-19528 > Project: Ignite > Issue Type: Improvement > Components: extensions >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > > Currently, there are no examples for different CDC configurations and > corresponding documentation. We need step-by-step documentation for > active-passive, active-active cases and for different clients and transports > (Ignite2Ignite, Ignite through Kafka). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18574) CDC: add documentation about Kafka request timeouts
[ https://issues.apache.org/jira/browse/IGNITE-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-18574: --- Assignee: Maksim Davydov (was: Alexey Gidaspov) > CDC: add documentation about Kafka request timeouts > --- > > Key: IGNITE-18574 > URL: https://issues.apache.org/jira/browse/IGNITE-18574 > Project: Ignite > Issue Type: Task > Components: documentation, extensions >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Time Spent: 1h 10m > Remaining Estimate: 0h > > We need to add more information information about timeouts configuration for > the CDC through Kafka. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-23085) Out of Memory preventive actions at startup
Maksim Davydov created IGNITE-23085: --- Summary: Out of Memory preventive actions at startup Key: IGNITE-23085 URL: https://issues.apache.org/jira/browse/IGNITE-23085 Project: Ignite Issue Type: Improvement Reporter: Maksim Davydov Assignee: Maksim Davydov Fix For: 2.17 There are cases, when the specified memory for Ignite (Heap, Data Regions ...) is not enough for correct and robust cluster performance. This case is checked at the startup and the corespoding WARNING is issued in the log. Nevertheless the log message is not very informative for the user, as it is hard to understand why the specified amount is insufficient. To work this issue out, I propose to add more information to the log message. It might help user to configure memory carefully in case the node crushes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22322) Removal of MVCC WAL record types
[
https://issues.apache.org/jira/browse/IGNITE-22322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov reassigned IGNITE-22322:
---
Assignee: Maksim Davydov
> Removal of MVCC WAL record types
>
>
> Key: IGNITE-22322
> URL: https://issues.apache.org/jira/browse/IGNITE-22322
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Ilya Shishkov
>Assignee: Maksim Davydov
>Priority: Minor
> Labels: ise
>
> Records type to remove:
> * {{RecordType.MVCC_DATA_PAGE_MARK_UPDATED_RECORD}}
> * {{RecordType.MVCC_DATA_PAGE_NEW_TX_STATE_HINT_UPDATED_RECORD}}
> * {{RecordType.MVCC_DATA_PAGE_TX_STATE_HINT_UPDATED_RECORD}}
> * {{RecordType.MVCC_DATA_RECORD}}
> * {{RecordType.MVCC_TX_RECORD}}
> + test on possible compatibility issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-23168) Event consumption time metric in CDC consumer
Maksim Davydov created IGNITE-23168: --- Summary: Event consumption time metric in CDC consumer Key: IGNITE-23168 URL: https://issues.apache.org/jira/browse/IGNITE-23168 Project: Ignite Issue Type: New Feature Components: extensions Reporter: Maksim Davydov Fix For: 2.17 Additonal metric for the total time the CDC consumer took to proccess the event -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23085) Out of Memory preventive actions at startup
[ https://issues.apache.org/jira/browse/IGNITE-23085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23085: Description: There are cases, when the specified memory for Ignite (Heap, Data Regions ...) is not enough for correct and robust cluster performance. This case is checked at the startup and the corespoding WARNING is issued in the log. Nevertheless the log message is not very informative for the user, as it is hard to understand why the specified amount is insufficient. To work this issue out, I propose to add more information to the log message. It might help user to configure memory carefully in case the node crushes. Changes: * Informative Warn message. * Required memory shouldn't exceed the physical RAM. was: There are cases, when the specified memory for Ignite (Heap, Data Regions ...) is not enough for correct and robust cluster performance. This case is checked at the startup and the corespoding WARNING is issued in the log. Nevertheless the log message is not very informative for the user, as it is hard to understand why the specified amount is insufficient. To work this issue out, I propose to add more information to the log message. It might help user to configure memory carefully in case the node crushes. > Out of Memory preventive actions at startup > --- > > Key: IGNITE-23085 > URL: https://issues.apache.org/jira/browse/IGNITE-23085 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > There are cases, when the specified memory for Ignite (Heap, Data Regions > ...) is not enough for correct and robust cluster performance. This case is > checked at the startup and the corespoding WARNING is issued in the log. > Nevertheless the log message is not very informative for the user, as it is > hard to understand why the specified amount is insufficient. > To work this issue out, I propose to add more information to the log message. > It might help user to configure memory carefully in case the node crushes. > Changes: > * Informative Warn message. > * Required memory shouldn't exceed the physical RAM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-23169) Histogram metrics for CDC put operations
[ https://issues.apache.org/jira/browse/IGNITE-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887889#comment-17887889 ] Maksim Davydov commented on IGNITE-23169: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc?branch=pull%2F287%2F&buildTypeTab=overview&mode=builds > Histogram metrics for CDC put operations > > > Key: IGNITE-23169 > URL: https://issues.apache.org/jira/browse/IGNITE-23169 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additional metric is needed for putAllConflict operations in CDC appliers -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-23168) Event consumption time metric in CDC consumer
[ https://issues.apache.org/jira/browse/IGNITE-23168 ] Maksim Davydov deleted comment on IGNITE-23168: - was (Author: JIRAUSER305006): Will be implemented in [IGNITE-23169|https://issues.apache.org/jira/browse/IGNITE-23169] > Event consumption time metric in CDC consumer > - > > Key: IGNITE-23168 > URL: https://issues.apache.org/jira/browse/IGNITE-23168 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additonal metric for the total time the CDC consumer took to proccess the > event -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23168) Event consumption time metric in CDC consumer
[ https://issues.apache.org/jira/browse/IGNITE-23168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23168: Description: Additonal metric for the total time the CDC consumer took to proccess the WAL segment events id needed with histogram metric for the operation duration. was:Additonal metric for the total time the CDC consumer took to proccess the event > Event consumption time metric in CDC consumer > - > > Key: IGNITE-23168 > URL: https://issues.apache.org/jira/browse/IGNITE-23168 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additonal metric for the total time the CDC consumer took to proccess the WAL > segment events id needed with histogram metric for the operation duration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23168) Event consumption time metric in CDC consumer
[ https://issues.apache.org/jira/browse/IGNITE-23168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23168: Description: Additonal metric for the total time the CDC consumer took to proccess the WAL segment events is needed with histogram metric for the operation duration. was: Additonal metric for the total time the CDC consumer took to proccess the WAL segment events id needed with histogram metric for the operation duration. > Event consumption time metric in CDC consumer > - > > Key: IGNITE-23168 > URL: https://issues.apache.org/jira/browse/IGNITE-23168 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additonal metric for the total time the CDC consumer took to proccess the WAL > segment events is needed with histogram metric for the operation duration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23168) Event consumption time metric in CDC consumer
[ https://issues.apache.org/jira/browse/IGNITE-23168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23168: Component/s: (was: extensions) > Event consumption time metric in CDC consumer > - > > Key: IGNITE-23168 > URL: https://issues.apache.org/jira/browse/IGNITE-23168 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additonal metric for the total time the CDC consumer took to proccess the WAL > segment events is needed with histogram metric for the operation duration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23168) Event consumption time metric in CDC consumer
[ https://issues.apache.org/jira/browse/IGNITE-23168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23168: Labels: ise (was: IEP-59 ise) > Event consumption time metric in CDC consumer > - > > Key: IGNITE-23168 > URL: https://issues.apache.org/jira/browse/IGNITE-23168 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Fix For: 2.17 > > > Additonal metric for the total time the CDC consumer took to proccess the WAL > segment events is needed with histogram metric for the operation duration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-23169) Histogram metrics for CDC put operations
[ https://issues.apache.org/jira/browse/IGNITE-23169 ] Maksim Davydov deleted comment on IGNITE-23169: - was (Author: JIRAUSER305006): https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc?branch=pull%2F287%2F&buildTypeTab=overview&mode=builds > Histogram metrics for CDC put operations > > > Key: IGNITE-23169 > URL: https://issues.apache.org/jira/browse/IGNITE-23169 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Fix For: 2.17 > > > Additional metric is needed for putAllConflict/removeAllConflict operations, > which are usede in CDC appliers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23169) Histogram metrics for CDC put operations
[ https://issues.apache.org/jira/browse/IGNITE-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23169: Description: Additional metric is needed for putAllConflict/removeAllConflict operations, which are usede in CDC appliers. (was: Additional metric is needed for putAllConflict operations in CDC appliers) > Histogram metrics for CDC put operations > > > Key: IGNITE-23169 > URL: https://issues.apache.org/jira/browse/IGNITE-23169 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additional metric is needed for putAllConflict/removeAllConflict operations, > which are usede in CDC appliers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23169) Histogram metrics for CDC put operations
[ https://issues.apache.org/jira/browse/IGNITE-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23169: Component/s: (was: extensions) > Histogram metrics for CDC put operations > > > Key: IGNITE-23169 > URL: https://issues.apache.org/jira/browse/IGNITE-23169 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additional metric is needed for putAllConflict/removeAllConflict operations, > which are usede in CDC appliers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23169) Histogram metrics for CDC put operations
[ https://issues.apache.org/jira/browse/IGNITE-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23169: Labels: ise (was: IEP-59 ise) > Histogram metrics for CDC put operations > > > Key: IGNITE-23169 > URL: https://issues.apache.org/jira/browse/IGNITE-23169 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Fix For: 2.17 > > > Additional metric is needed for putAllConflict/removeAllConflict operations, > which are usede in CDC appliers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-23168) Event consumption time metric in CDC consumer
[ https://issues.apache.org/jira/browse/IGNITE-23168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883596#comment-17883596 ] Maksim Davydov commented on IGNITE-23168: - Will be implemented in [IGNITE-23169|https://issues.apache.org/jira/browse/IGNITE-23169] > Event consumption time metric in CDC consumer > - > > Key: IGNITE-23168 > URL: https://issues.apache.org/jira/browse/IGNITE-23168 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-59, ise > Fix For: 2.17 > > > Additonal metric for the total time the CDC consumer took to proccess the > event -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21927) Removal of MVCC-related code from JDBC classes
[ https://issues.apache.org/jira/browse/IGNITE-21927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-21927: Description: Classes to remove # NestedTxMode JDBC code must be complaint with a scpecification (see IGNITE-5339). Changes must provide full compatibility with older versions of servers and clients. was: Classes to remove # NestedTxMode # Remove txAllowed flag in JdbcConnection JDBC code must be complaint with a scpecification (see IGNITE-5339). Changes must provide full compatibility with older versions of servers and clients. > Removal of MVCC-related code from JDBC classes > -- > > Key: IGNITE-21927 > URL: https://issues.apache.org/jira/browse/IGNITE-21927 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Time Spent: 2.5h > Remaining Estimate: 0h > > Classes to remove > # NestedTxMode > JDBC code must be complaint with a scpecification (see IGNITE-5339). Changes > must provide full compatibility with older versions of servers and clients. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-23901) Add operation time performance statistics for putAllConflict, removeAllConflict
Maksim Davydov created IGNITE-23901: --- Summary: Add operation time performance statistics for putAllConflict, removeAllConflict Key: IGNITE-23901 URL: https://issues.apache.org/jira/browse/IGNITE-23901 Project: Ignite Issue Type: New Feature Reporter: Maksim Davydov Assignee: Maksim Davydov Performance statisitcs tracking is needed for #putAllConflict() and #removeAllConflict() cache operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24083) Remove MIN_BLT_SUPPORTING_VER
[ https://issues.apache.org/jira/browse/IGNITE-24083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908648#comment-17908648 ] Maksim Davydov commented on IGNITE-24083: - All blockers on the last visa are flaky, failing on master, and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] > Remove MIN_BLT_SUPPORTING_VER > - > > Key: IGNITE-24083 > URL: https://issues.apache.org/jira/browse/IGNITE-24083 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24084) Remove VerifyBackupPartitionsTaskV2#V2_SINCE_VER
[ https://issues.apache.org/jira/browse/IGNITE-24084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24084: --- Assignee: Maksim Davydov > Remove VerifyBackupPartitionsTaskV2#V2_SINCE_VER > > > Key: IGNITE-24084 > URL: https://issues.apache.org/jira/browse/IGNITE-24084 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24081) Remove TX_PME_TIMEOUT_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908645#comment-17908645 ] Maksim Davydov commented on IGNITE-24081: - All blockers on the last visa are flaky, failing on master and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] > Remove TX_PME_TIMEOUT_SINCE > --- > > Key: IGNITE-24081 > URL: https://issues.apache.org/jira/browse/IGNITE-24081 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 0.5h > Remaining Estimate: 0h > > https://issues.apache.org/jira/browse/IGNITE-24082 is implemented here as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-24081) Remove TX_PME_TIMEOUT_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908645#comment-17908645 ] Maksim Davydov edited comment on IGNITE-24081 at 12/28/24 7:09 PM: --- All blockers on the last visa are flaky, failing on master, and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] was (Author: JIRAUSER305006): All blockers on the last visa are flaky, failing on master and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] > Remove TX_PME_TIMEOUT_SINCE > --- > > Key: IGNITE-24081 > URL: https://issues.apache.org/jira/browse/IGNITE-24081 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 0.5h > Remaining Estimate: 0h > > https://issues.apache.org/jira/browse/IGNITE-24082 is implemented here as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24090) Remove EXCHANGE_PROTOCOL_2_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24090: --- Assignee: Maksim Davydov > Remove EXCHANGE_PROTOCOL_2_SINCE > > > Key: IGNITE-24090 > URL: https://issues.apache.org/jira/browse/IGNITE-24090 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24085) Remove CACHE_ENCRYPTION_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24085: --- Assignee: Maksim Davydov > Remove CACHE_ENCRYPTION_SINCE > - > > Key: IGNITE-24085 > URL: https://issues.apache.org/jira/browse/IGNITE-24085 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-23901) Add operation time performance statistics for putAllConflict, removeAllConflict
[ https://issues.apache.org/jira/browse/IGNITE-23901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923290#comment-17923290 ] Maksim Davydov commented on IGNITE-23901: - Visa: https://tcbot2.sbt-ignite-dev.ru/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/11793/head&action=Latest > Add operation time performance statistics for putAllConflict, > removeAllConflict > --- > > Key: IGNITE-23901 > URL: https://issues.apache.org/jira/browse/IGNITE-23901 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-35, ise > Time Spent: 7h 20m > Remaining Estimate: 0h > > Performance statisitcs tracking is needed for #putAllConflict() and > #removeAllConflict() cache operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-24362) Fix CacheExchangeMessageDuplicatedStateTest
Maksim Davydov created IGNITE-24362: --- Summary: Fix CacheExchangeMessageDuplicatedStateTest Key: IGNITE-24362 URL: https://issues.apache.org/jira/browse/IGNITE-24362 Project: Ignite Issue Type: Bug Reporter: Maksim Davydov Assignee: Maksim Davydov Fix For: 2.18 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24093) Remove PARTIAL_COUNTERS_MAP_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24093: Fix Version/s: 2.18 > Remove PARTIAL_COUNTERS_MAP_SINCE > - > > Key: IGNITE-24093 > URL: https://issues.apache.org/jira/browse/IGNITE-24093 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-23901) Add operation time performance statistics for putAllConflict, removeAllConflict
[ https://issues.apache.org/jira/browse/IGNITE-23901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923133#comment-17923133 ] Maksim Davydov commented on IGNITE-23901: - Extensions visa: https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_PerformanceStatistics?branch=pull%2F299%2F#all-projects > Add operation time performance statistics for putAllConflict, > removeAllConflict > --- > > Key: IGNITE-23901 > URL: https://issues.apache.org/jira/browse/IGNITE-23901 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Time Spent: 7h 20m > Remaining Estimate: 0h > > Performance statisitcs tracking is needed for #putAllConflict() and > #removeAllConflict() cache operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23901) Add operation time performance statistics for putAllConflict, removeAllConflict
[ https://issues.apache.org/jira/browse/IGNITE-23901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23901: Labels: IEP-35 ise (was: ise) > Add operation time performance statistics for putAllConflict, > removeAllConflict > --- > > Key: IGNITE-23901 > URL: https://issues.apache.org/jira/browse/IGNITE-23901 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: IEP-35, ise > Time Spent: 7h 20m > Remaining Estimate: 0h > > Performance statisitcs tracking is needed for #putAllConflict() and > #removeAllConflict() cache operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23901) Add operation time performance statistics for putAllConflict, removeAllConflict
[ https://issues.apache.org/jira/browse/IGNITE-23901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23901: Component/s: extensions > Add operation time performance statistics for putAllConflict, > removeAllConflict > --- > > Key: IGNITE-23901 > URL: https://issues.apache.org/jira/browse/IGNITE-23901 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Minor > Labels: ise > Time Spent: 7h 20m > Remaining Estimate: 0h > > Performance statisitcs tracking is needed for #putAllConflict() and > #removeAllConflict() cache operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24362) Fix CacheExchangeMessageDuplicatedStateTest
[ https://issues.apache.org/jira/browse/IGNITE-24362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922568#comment-17922568 ] Maksim Davydov commented on IGNITE-24362: - Suit is fixed https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache2?branch=pull%2F11842%2Fhead&page=1 > Fix CacheExchangeMessageDuplicatedStateTest > --- > > Key: IGNITE-24362 > URL: https://issues.apache.org/jira/browse/IGNITE-24362 > Project: Ignite > Issue Type: Test >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: ise > Fix For: 2.18 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-24362) Fix CacheExchangeMessageDuplicatedStateTest
[ https://issues.apache.org/jira/browse/IGNITE-24362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922568#comment-17922568 ] Maksim Davydov edited comment on IGNITE-24362 at 1/31/25 5:25 AM: -- Suite is fixed https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache2?branch=pull%2F11842%2Fhead&page=1 was (Author: JIRAUSER305006): Suit is fixed https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache2?branch=pull%2F11842%2Fhead&page=1 > Fix CacheExchangeMessageDuplicatedStateTest > --- > > Key: IGNITE-24362 > URL: https://issues.apache.org/jira/browse/IGNITE-24362 > Project: Ignite > Issue Type: Test >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: ise > Fix For: 2.18 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24362) Fix CacheExchangeMessageDuplicatedStateTest
[ https://issues.apache.org/jira/browse/IGNITE-24362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24362: Priority: Major (was: Blocker) > Fix CacheExchangeMessageDuplicatedStateTest > --- > > Key: IGNITE-24362 > URL: https://issues.apache.org/jira/browse/IGNITE-24362 > Project: Ignite > Issue Type: Test >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: ise > Fix For: 2.18 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24362) Fix CacheExchangeMessageDuplicatedStateTest
[ https://issues.apache.org/jira/browse/IGNITE-24362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24362: Issue Type: Test (was: Bug) > Fix CacheExchangeMessageDuplicatedStateTest > --- > > Key: IGNITE-24362 > URL: https://issues.apache.org/jira/browse/IGNITE-24362 > Project: Ignite > Issue Type: Test >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Blocker > Labels: ise > Fix For: 2.18 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24260) Remove IgniteDataTransferObject#Vxx usage
[ https://issues.apache.org/jira/browse/IGNITE-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24260: Labels: IEP-132 ise (was: ISE-132 ise) > Remove IgniteDataTransferObject#Vxx usage > - > > Key: IGNITE-24260 > URL: https://issues.apache.org/jira/browse/IGNITE-24260 > Project: Ignite > Issue Type: Task >Reporter: Nikolay Izhikov >Priority: Major > Labels: IEP-132, ise > > IgniteDataTransferObject provides several fields to improve sucessors in > compatible way: > V1, V2 ... V9. > Currently, Ignite don't provide any versions runtime compatibility, so we can > safely remove fields and usages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-23085) Out of Memory preventive actions at startup
[ https://issues.apache.org/jira/browse/IGNITE-23085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-23085: Description: There are cases, when the specified memory for Ignite (Heap, Data Regions ...) is not enough for correct and robust cluster performance. This case is checked at the startup and the corespoding WARNING is issued in the log. Nevertheless the log message is not very informative for the user, as it is hard to understand why the specified amount is insufficient. To work this issue out, I propose to add more information to the log message. It might help user to configure memory carefully in case the node crushes. Changes: * Informative Warn message. was: There are cases, when the specified memory for Ignite (Heap, Data Regions ...) is not enough for correct and robust cluster performance. This case is checked at the startup and the corespoding WARNING is issued in the log. Nevertheless the log message is not very informative for the user, as it is hard to understand why the specified amount is insufficient. To work this issue out, I propose to add more information to the log message. It might help user to configure memory carefully in case the node crushes. Changes: * Informative Warn message. * Required memory shouldn't exceed the physical RAM. > Out of Memory preventive actions at startup > --- > > Key: IGNITE-23085 > URL: https://issues.apache.org/jira/browse/IGNITE-23085 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > There are cases, when the specified memory for Ignite (Heap, Data Regions > ...) is not enough for correct and robust cluster performance. This case is > checked at the startup and the corespoding WARNING is issued in the log. > Nevertheless the log message is not very informative for the user, as it is > hard to understand why the specified amount is insufficient. > To work this issue out, I propose to add more information to the log message. > It might help user to configure memory carefully in case the node crushes. > Changes: > * Informative Warn message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24085) Remove CACHE_ENCRYPTION_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24085: Fix Version/s: 2.18 > Remove CACHE_ENCRYPTION_SINCE > - > > Key: IGNITE-24085 > URL: https://issues.apache.org/jira/browse/IGNITE-24085 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24081) Remove TX_PME_TIMEOUT_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24081: Fix Version/s: 2.18 > Remove TX_PME_TIMEOUT_SINCE > --- > > Key: IGNITE-24081 > URL: https://issues.apache.org/jira/browse/IGNITE-24081 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 50m > Remaining Estimate: 0h > > https://issues.apache.org/jira/browse/IGNITE-24082 is implemented here as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24082) Remove DEADLOCK_TIMEOUT_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24082: Fix Version/s: 2.18 > Remove DEADLOCK_TIMEOUT_SINCE > - > > Key: IGNITE-24082 > URL: https://issues.apache.org/jira/browse/IGNITE-24082 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24086) Remove V_MERGE_CONFIG_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24086: Fix Version/s: 2.18 > Remove V_MERGE_CONFIG_SINCE > --- > > Key: IGNITE-24086 > URL: https://issues.apache.org/jira/browse/IGNITE-24086 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24083) Remove MIN_BLT_SUPPORTING_VER
[ https://issues.apache.org/jira/browse/IGNITE-24083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24083: Fix Version/s: 2.18 > Remove MIN_BLT_SUPPORTING_VER > - > > Key: IGNITE-24083 > URL: https://issues.apache.org/jira/browse/IGNITE-24083 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24084) Remove VerifyBackupPartitionsTaskV2#V2_SINCE_VER
[ https://issues.apache.org/jira/browse/IGNITE-24084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24084: Fix Version/s: 2.18 > Remove VerifyBackupPartitionsTaskV2#V2_SINCE_VER > > > Key: IGNITE-24084 > URL: https://issues.apache.org/jira/browse/IGNITE-24084 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24178) Remove idleVerifyV1 related code
[ https://issues.apache.org/jira/browse/IGNITE-24178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24178: Fix Version/s: 2.18 > Remove idleVerifyV1 related code > > > Key: IGNITE-24178 > URL: https://issues.apache.org/jira/browse/IGNITE-24178 > Project: Ignite > Issue Type: Sub-task >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 1h > Remaining Estimate: 0h > > The code related to the old idleVerifyV1 task is still present in the code > base. Since it is not used the classes like > RetrieveConflictPartitionValuesTask, CollectConflictPartitionKeysTask, and > related code need to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24090) Remove EXCHANGE_PROTOCOL_2_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24090: Fix Version/s: 2.18 > Remove EXCHANGE_PROTOCOL_2_SINCE > > > Key: IGNITE-24090 > URL: https://issues.apache.org/jira/browse/IGNITE-24090 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24092) Remove PRECISION_SCALE_SINCE_VER
[ https://issues.apache.org/jira/browse/IGNITE-24092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24092: Fix Version/s: 2.18 > Remove PRECISION_SCALE_SINCE_VER > > > Key: IGNITE-24092 > URL: https://issues.apache.org/jira/browse/IGNITE-24092 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24087) Remove PRELOAD_PARTITION_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24087: Fix Version/s: 2.18 > Remove PRELOAD_PARTITION_SINCE > -- > > Key: IGNITE-24087 > URL: https://issues.apache.org/jira/browse/IGNITE-24087 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24091) Remove CONT_QRY_WITH_TRANSFORMER_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24091: Fix Version/s: 2.18 > Remove CONT_QRY_WITH_TRANSFORMER_SINCE > -- > > Key: IGNITE-24091 > URL: https://issues.apache.org/jira/browse/IGNITE-24091 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Fix For: 2.18 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-23756) Spring Data: Add support for type converters
[
https://issues.apache.org/jira/browse/IGNITE-23756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916723#comment-17916723
]
Maksim Davydov commented on IGNITE-23756:
-
[~anovikov] [~myskov] Code style fails. Your TC test failed on build with
{code}
Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:check (style) on project
ignite-spring-data-ext: Failed during checkstyle execution: There are 30 errors
reported by Checkstyle 8.45 with checkstyle/checkstyle.xml ruleset.
{code}
The module spring-data-ext is also failing with
{code}
mvn clean install -f modules/spring-data-ext -Pcheckstyle -DskipTests
{code}
Can you fix it?
> Spring Data: Add support for type converters
>
>
> Key: IGNITE-23756
> URL: https://issues.apache.org/jira/browse/IGNITE-23756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maksim Myskov
>Assignee: Maksim Myskov
>Priority: Major
>
> The current spring data extension has issues with working with LocalDateTime
> type.
> LocalDateTime maps to Ignite's Timestamp, but it cannot be converted
> automatically.
>
> {code:java}
> java.lang.IllegalArgumentException: Can not set java.time.LocalDateTime field
> Person.createdAt to java.sql.Timestamp {code}
> We need to get support for spring data converters
> [https://docs.spring.io/spring-data/jpa/reference/data-commons/custom-conversions.html.]
>
> Reproduce scenario:
> {code:java}
> package util;
> import java.time.LocalDateTime;
> import java.util.List;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.query.SqlFieldsQuery;
> import org.apache.ignite.cache.query.annotations.QuerySqlField;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> public class LocalDateTimeChecker {
> // Person POJO with annotations
> public static class Person {
> @QuerySqlField(index = true)
> private int id;
> @QuerySqlField
> private String name;
>
> @QuerySqlField
> private LocalDateTime createdAt;
> public Person() {}
> public Person(int id, String name, LocalDateTime createdAt) {
> this.id = id;
> this.name = name;
> this.createdAt = createdAt;
> }
> // Getters and setters
> public int getId() { return id; }
> public void setId(int id) { this.id = id; }
> public String getName() { return name; }
> public void setName(String name) { this.name = name; }
> public LocalDateTime getCreatedAt() { return createdAt; }
> public void setCreatedAt(LocalDateTime createdAt) { this.createdAt =
> createdAt; }
> }
> public static void main(String[] args) {
> // Configure Ignite
> IgniteConfiguration cfg = new IgniteConfiguration(); //
> Configure cache
> CacheConfiguration cacheCfg = new
> CacheConfiguration<>("PersonCache");
> cacheCfg.setIndexedTypes(Integer.class, Person.class);
> cfg.setCacheConfiguration(cacheCfg); // Start Ignite
> try (Ignite ignite = Ignition.start(cfg)) {
> // Get cache
> IgniteCache cache =
> ignite.getOrCreateCache(cacheCfg); // Insert data
> LocalDateTime now = LocalDateTime.now();
> cache.put(1, new Person(1, "John Doe", now));
> cache.put(2, new Person(2, "Jane Smith", now.plusDays(1)));
> // Query using custom function
> SqlFieldsQuery query = new SqlFieldsQuery(
> "SELECT id, name, asLocalDateTime(createdAt) FROM Person"
> ); // Execute query and print results with types
> List> results = cache.query(query).getAll();
> for (List row : results) {
> System.out.println("Row data:");
> for (Object field : row) {
> System.out.println("Value: " + field +
> ", Type: " + (field != null ?
> field.getClass().getName() : "null"));
> }
> System.out.println("---");
> }
> }
> }
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-24102) Remove VERSION_SINCE_CLIENT_COULD_WAIT_TO_CONNECT
[ https://issues.apache.org/jira/browse/IGNITE-24102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914665#comment-17914665 ] Maksim Davydov commented on IGNITE-24102: - https://tcbot2.sbt-ignite-dev.ru/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/11821/head&action=Latest > Remove VERSION_SINCE_CLIENT_COULD_WAIT_TO_CONNECT > - > > Key: IGNITE-24102 > URL: https://issues.apache.org/jira/browse/IGNITE-24102 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24093) Remove PARTIAL_COUNTERS_MAP_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914703#comment-17914703 ] Maksim Davydov commented on IGNITE-24093: - https://tcbot2.sbt-ignite-dev.ru/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/11820/head&action=Latest > Remove PARTIAL_COUNTERS_MAP_SINCE > - > > Key: IGNITE-24093 > URL: https://issues.apache.org/jira/browse/IGNITE-24093 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-23085) Out of Memory preventive actions at startup
[ https://issues.apache.org/jira/browse/IGNITE-23085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921710#comment-17921710 ] Maksim Davydov commented on IGNITE-23085: - https://tcbot2.sbt-ignite-dev.ru/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/11502/head&action=Latest > Out of Memory preventive actions at startup > --- > > Key: IGNITE-23085 > URL: https://issues.apache.org/jira/browse/IGNITE-23085 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > Time Spent: 0.5h > Remaining Estimate: 0h > > There are cases, when the specified memory for Ignite (Heap, Data Regions > ...) is not enough for correct and robust cluster performance. This case is > checked at the startup and the corespoding WARNING is issued in the log. > Nevertheless the log message is not very informative for the user, as it is > hard to understand why the specified amount is insufficient. > To work this issue out, I propose to add more information to the log message. > It might help user to configure memory carefully in case the node crushes. > Changes: > * Informative Warn message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-24270) Change IdleVerifyResult output
Maksim Davydov created IGNITE-24270: --- Summary: Change IdleVerifyResult output Key: IGNITE-24270 URL: https://issues.apache.org/jira/browse/IGNITE-24270 Project: Ignite Issue Type: Task Reporter: Maksim Davydov IdleVerifyResult#printConflicts(Consumer) output depends on code-specific class naming, like PartitionKey#toString(), and PartitionHashRecord#toString() It's better to change the output, so that the IdleVerify command output doesn't depend on class naming -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24178) Remove idleVerifyV1 related code
[ https://issues.apache.org/jira/browse/IGNITE-24178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914958#comment-17914958 ] Maksim Davydov commented on IGNITE-24178: - https://tcbot2.sbt-ignite-dev.ru/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/11801/head&action=Latest > Remove idleVerifyV1 related code > > > Key: IGNITE-24178 > URL: https://issues.apache.org/jira/browse/IGNITE-24178 > Project: Ignite > Issue Type: Sub-task >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 50m > Remaining Estimate: 0h > > The code related to the old idleVerifyV1 task is still present in the code > base. Since it is not used the classes like > RetrieveConflictPartitionValuesTask, CollectConflictPartitionKeysTask, and > related code need to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24157) LastArchivedSegment metric for WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-24157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916936#comment-17916936 ] Maksim Davydov commented on IGNITE-24157: - https://tcbot2.sbt-ignite-dev.ru/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/11794/head&action=Latest > LastArchivedSegment metric for WAL archive > -- > > Key: IGNITE-24157 > URL: https://issues.apache.org/jira/browse/IGNITE-24157 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: ise > Time Spent: 10m > Remaining Estimate: 0h > > With new metric 'LastArchivedSegment' we can track the current index of WAL > file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24092) Remove PRECISION_SCALE_SINCE_VER
[ https://issues.apache.org/jira/browse/IGNITE-24092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24092: --- Assignee: Maksim Davydov > Remove PRECISION_SCALE_SINCE_VER > > > Key: IGNITE-24092 > URL: https://issues.apache.org/jira/browse/IGNITE-24092 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24091) Remove CONT_QRY_WITH_TRANSFORMER_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24091: --- Assignee: Maksim Davydov > Remove CONT_QRY_WITH_TRANSFORMER_SINCE > -- > > Key: IGNITE-24091 > URL: https://issues.apache.org/jira/browse/IGNITE-24091 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24093) Remove PARTIAL_COUNTERS_MAP_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24093: --- Assignee: Maksim Davydov > Remove PARTIAL_COUNTERS_MAP_SINCE > - > > Key: IGNITE-24093 > URL: https://issues.apache.org/jira/browse/IGNITE-24093 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-24191) Remove IGNITE_EXCHANGE_COMPATIBILITY_VER_1
Maksim Davydov created IGNITE-24191: --- Summary: Remove IGNITE_EXCHANGE_COMPATIBILITY_VER_1 Key: IGNITE-24191 URL: https://issues.apache.org/jira/browse/IGNITE-24191 Project: Ignite Issue Type: Sub-task Reporter: Maksim Davydov Assignee: Maksim Davydov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24086) Remove V_MERGE_CONFIG_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24086: --- Assignee: Maksim Davydov > Remove V_MERGE_CONFIG_SINCE > --- > > Key: IGNITE-24086 > URL: https://issues.apache.org/jira/browse/IGNITE-24086 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-24087) Remove PRELOAD_PARTITION_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov reassigned IGNITE-24087: --- Assignee: Maksim Davydov > Remove PRELOAD_PARTITION_SINCE > -- > > Key: IGNITE-24087 > URL: https://issues.apache.org/jira/browse/IGNITE-24087 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-24157) WalCdcArchiveSegments persistance metric for CDC workflow
Maksim Davydov created IGNITE-24157: --- Summary: WalCdcArchiveSegments persistance metric for CDC workflow Key: IGNITE-24157 URL: https://issues.apache.org/jira/browse/IGNITE-24157 Project: Ignite Issue Type: New Feature Reporter: Maksim Davydov Assignee: Maksim Davydov 'WalArchiveSegments' metric introduced for WAL archive allows users to monitor the archive directory to prevent its the potential overflow. But there is no such thing for CDC WAL archive. With 'DataStorageConfiguration#cdcWalDirectoryMaxSize()' set to default there is no limit on the CDC WAL archive size. And in case the CDC clients are stopped the server node will continiue to flood the directory until there is no space left on the disk. With new metric 'CdcWalArchiveSegments' we can track the remaining number of WAL segments to be processed by CDC clients -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24084) Remove VerifyBackupPartitionsTaskV2#V2_SINCE_VER
[ https://issues.apache.org/jira/browse/IGNITE-24084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909894#comment-17909894 ] Maksim Davydov commented on IGNITE-24084: - All blockers on the last visa are flaky, failing on master, and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] > Remove VerifyBackupPartitionsTaskV2#V2_SINCE_VER > > > Key: IGNITE-24084 > URL: https://issues.apache.org/jira/browse/IGNITE-24084 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24085) Remove CACHE_ENCRYPTION_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909897#comment-17909897 ] Maksim Davydov commented on IGNITE-24085: - All blockers on the last visa are flaky, failing on master, and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] > Remove CACHE_ENCRYPTION_SINCE > - > > Key: IGNITE-24085 > URL: https://issues.apache.org/jira/browse/IGNITE-24085 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-24157) CdcWalArchiveSegments persistance metric for CDC workflow
[ https://issues.apache.org/jira/browse/IGNITE-24157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Davydov updated IGNITE-24157: Summary: CdcWalArchiveSegments persistance metric for CDC workflow (was: WalCdcArchiveSegments persistance metric for CDC workflow) > CdcWalArchiveSegments persistance metric for CDC workflow > - > > Key: IGNITE-24157 > URL: https://issues.apache.org/jira/browse/IGNITE-24157 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Davydov >Assignee: Maksim Davydov >Priority: Major > Labels: ise > > 'WalArchiveSegments' metric introduced for WAL archive allows users to > monitor the archive directory to prevent its the potential overflow. But > there is no such thing for CDC WAL archive. > With 'DataStorageConfiguration#cdcWalDirectoryMaxSize()' set to default there > is no limit on the CDC WAL archive size. And in case the CDC clients are > stopped the server node will continiue to flood the directory until there is > no space left on the disk. > With new metric 'CdcWalArchiveSegments' we can track the remaining number of > WAL segments to be processed by CDC clients -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24083) Remove MIN_BLT_SUPPORTING_VER
[ https://issues.apache.org/jira/browse/IGNITE-24083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909908#comment-17909908 ] Maksim Davydov commented on IGNITE-24083: - All blockers on the last visa are flaky, failing on master, and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] > Remove MIN_BLT_SUPPORTING_VER > - > > Key: IGNITE-24083 > URL: https://issues.apache.org/jira/browse/IGNITE-24083 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24086) Remove V_MERGE_CONFIG_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909910#comment-17909910 ] Maksim Davydov commented on IGNITE-24086: - All blockers on the last visa are flaky, failing on master, and have fail rate > 50% according to [teamcity|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects] > Remove V_MERGE_CONFIG_SINCE > --- > > Key: IGNITE-24086 > URL: https://issues.apache.org/jira/browse/IGNITE-24086 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-24082) Remove DEADLOCK_TIMEOUT_SINCE
[ https://issues.apache.org/jira/browse/IGNITE-24082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908117#comment-17908117 ] Maksim Davydov commented on IGNITE-24082: - Will be implemented in https://issues.apache.org/jira/browse/IGNITE-24081 > Remove DEADLOCK_TIMEOUT_SINCE > - > > Key: IGNITE-24082 > URL: https://issues.apache.org/jira/browse/IGNITE-24082 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Maksim Davydov >Priority: Major > Labels: IEP-132, ise > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
