[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=17864702#comment-17864702 ] Maksim Davydov commented on IGNITE-22670: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7954843?expandBuildDeploymentsSection=false=false=false=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] [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=17864080#comment-17864080 ] Maksim Davydov commented on IGNITE-22403: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7975381?hideProblemsFromDependencies=false=false=false=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] [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=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=false=false=true was (Author: JIRAUSER305006): https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7955206?hideTestsFromDependencies=false=false=false=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] [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=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=false=false=true was (Author: JIRAUSER305006): https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7902745?buildTab=overview=false=false=true=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] [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] [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] [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=17863071#comment-17863071 ] Maksim Davydov commented on IGNITE-22536: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7948184?hideTestsFromDependencies=false=false=false=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] [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] [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] [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] [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] [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=17852832#comment-17852832 ] Maksim Davydov commented on IGNITE-22403: - https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7902745?buildTab=overview=false=false=true=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-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] [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-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] [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 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] [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] (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] [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=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] [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)
