[jira] [Updated] (IGNITE-12844) Too many caches can block discovery
[ https://issues.apache.org/jira/browse/IGNITE-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Masharov updated IGNITE-12844: -- Reviewer: Anton Kalashnikov (was: Ivan Bessonov) > Too many caches can block discovery > --- > > Key: IGNITE-12844 > URL: https://issues.apache.org/jira/browse/IGNITE-12844 > Project: Ignite > Issue Type: Bug >Reporter: Philipp Masharov >Assignee: Philipp Masharov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Several thousand caches send metrics in each discovery message. > Check implementation of `TcpDiscoveryMetricsUpdateMessage` > This behavior increases processing time and raises message size. As a > result, the discovery worker is busy and the queue pool is growing. > We need to notify about the possible issue and print a suggestion, for > example, `-DIGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=true` if it can > help. Assumes to print WARN message once, for example, if > TcpDiscoveryMetricsUpdateMessage consists of more than 500 > CacheMetricsSnaphot instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12844) Too many caches can block discovery
[ https://issues.apache.org/jira/browse/IGNITE-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070374#comment-17070374 ] Philipp Masharov commented on IGNITE-12844: --- [~zstan] Thanks! I've fixed the description. In the code, the property named correctly. The actual name of the property IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE > Too many caches can block discovery > --- > > Key: IGNITE-12844 > URL: https://issues.apache.org/jira/browse/IGNITE-12844 > Project: Ignite > Issue Type: Bug >Reporter: Philipp Masharov >Assignee: Philipp Masharov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Several thousand caches send metrics in each discovery message. > Check implementation of `TcpDiscoveryMetricsUpdateMessage` > This behavior increases processing time and raises message size. As a > result, the discovery worker is busy and the queue pool is growing. > We need to notify about the possible issue and print a suggestion, for > example, `-DIGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=true` if it can > help. Assumes to print WARN message once, for example, if > TcpDiscoveryMetricsUpdateMessage consists of more than 500 > CacheMetricsSnaphot instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12844) Too many caches can block discovery
[ https://issues.apache.org/jira/browse/IGNITE-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Masharov updated IGNITE-12844: -- Description: Several thousand caches send metrics in each discovery message. Check implementation of `TcpDiscoveryMetricsUpdateMessage` This behavior increases processing time and raises message size. As a result, the discovery worker is busy and the queue pool is growing. We need to notify about the possible issue and print a suggestion, for example, `-DIGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=true` if it can help. Assumes to print WARN message once, for example, if TcpDiscoveryMetricsUpdateMessage consists of more than 500 CacheMetricsSnaphot instances. was: Several thousand caches send metrics in each discovery message. Check implementation of `TcpDiscoveryMetricsUpdateMessage` This behavior increases processing time and raises message size. As a result, the discovery worker is busy and the queue pool is growing. We need to notify about the possible issue and print suggestion, for example, `-DIGNITE_DISCOVERY_DISABLE_CACHE=true` if it can help. Assumes to print WARN message once, for example, if TcpDiscoveryMetricsUpdateMessage consists of more than 500 CacheMetricsSnaphot instances. > Too many caches can block discovery > --- > > Key: IGNITE-12844 > URL: https://issues.apache.org/jira/browse/IGNITE-12844 > Project: Ignite > Issue Type: Bug >Reporter: Philipp Masharov >Assignee: Philipp Masharov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Several thousand caches send metrics in each discovery message. > Check implementation of `TcpDiscoveryMetricsUpdateMessage` > This behavior increases processing time and raises message size. As a > result, the discovery worker is busy and the queue pool is growing. > We need to notify about the possible issue and print a suggestion, for > example, `-DIGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=true` if it can > help. Assumes to print WARN message once, for example, if > TcpDiscoveryMetricsUpdateMessage consists of more than 500 > CacheMetricsSnaphot instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12844) Too many caches can block discovery
[ https://issues.apache.org/jira/browse/IGNITE-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Masharov updated IGNITE-12844: -- Reviewer: Ivan Bessonov > Too many caches can block discovery > --- > > Key: IGNITE-12844 > URL: https://issues.apache.org/jira/browse/IGNITE-12844 > Project: Ignite > Issue Type: Bug >Reporter: Philipp Masharov >Assignee: Philipp Masharov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Several thousand caches send metrics in each discovery message. > Check implementation of `TcpDiscoveryMetricsUpdateMessage` > This behavior increases processing time and raises message size. As a result, > the discovery worker is busy and the queue pool is growing. > We need to notify about the possible issue and print suggestion, for example, > `-DIGNITE_DISCOVERY_DISABLE_CACHE=true` if it can help. Assumes to print WARN > message once, for example, if TcpDiscoveryMetricsUpdateMessage consists of > more than 500 CacheMetricsSnaphot instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12844) Too many caches can block discovery
[ https://issues.apache.org/jira/browse/IGNITE-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Masharov updated IGNITE-12844: -- Release Note: A log message on how to avoid discovery blocking because of too many cache metrics was added. > Too many caches can block discovery > --- > > Key: IGNITE-12844 > URL: https://issues.apache.org/jira/browse/IGNITE-12844 > Project: Ignite > Issue Type: Bug >Reporter: Philipp Masharov >Assignee: Philipp Masharov >Priority: Major > Fix For: 2.9 > > > Several thousand caches send metrics in each discovery message. > Check implementation of `TcpDiscoveryMetricsUpdateMessage` > This behavior increases processing time and raises message size. As a result, > the discovery worker is busy and the queue pool is growing. > We need to notify about the possible issue and print suggestion, for example, > `-DIGNITE_DISCOVERY_DISABLE_CACHE=true` if it can help. Assumes to print WARN > message once, for example, if TcpDiscoveryMetricsUpdateMessage consists of > more than 500 CacheMetricsSnaphot instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12844) Too many caches can block discovery
Philipp Masharov created IGNITE-12844: - Summary: Too many caches can block discovery Key: IGNITE-12844 URL: https://issues.apache.org/jira/browse/IGNITE-12844 Project: Ignite Issue Type: Bug Reporter: Philipp Masharov Assignee: Philipp Masharov Fix For: 2.9 Several thousand caches send metrics in each discovery message. Check implementation of `TcpDiscoveryMetricsUpdateMessage` This behavior increases processing time and raises message size. As a result, the discovery worker is busy and the queue pool is growing. We need to notify about the possible issue and print suggestion, for example, `-DIGNITE_DISCOVERY_DISABLE_CACHE=true` if it can help. Assumes to print WARN message once, for example, if TcpDiscoveryMetricsUpdateMessage consists of more than 500 CacheMetricsSnaphot instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12761) Add ability to disable check crc sums of stored pages due to invalidate_indexes.
[ https://issues.apache.org/jira/browse/IGNITE-12761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062552#comment-17062552 ] Philipp Masharov commented on IGNITE-12761: --- [~slava.koptilin]Thanks! I replied to the comment. > Add ability to disable check crc sums of stored pages due to > invalidate_indexes. > > > Key: IGNITE-12761 > URL: https://issues.apache.org/jira/browse/IGNITE-12761 > Project: Ignite > Issue Type: Bug >Reporter: Philipp Masharov >Assignee: Philipp Masharov >Priority: Major > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add additional param to validate_indexes command > org.apache.ignite.internal.commandline.cache.CacheSubcommands#VALIDATE_INDEXES*like > here: > org.apache.ignite.internal.commandline.cache.argument.IdleVerifyCommandArg#CHECK_CRC > now by default this check is always enabled, need to be configurable like the > same one in IdleVerifyCommandArg -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12761) Add ability to disable check crc sums of stored pages due to invalidate_indexes.
Philipp Masharov created IGNITE-12761: - Summary: Add ability to disable check crc sums of stored pages due to invalidate_indexes. Key: IGNITE-12761 URL: https://issues.apache.org/jira/browse/IGNITE-12761 Project: Ignite Issue Type: Bug Reporter: Philipp Masharov Assignee: Philipp Masharov Add additional param to validate_indexes command org.apache.ignite.internal.commandline.cache.CacheSubcommands#VALIDATE_INDEXES*like here: org.apache.ignite.internal.commandline.cache.argument.IdleVerifyCommandArg#CHECK_CRC now by default this check is always enabled, need to be configurable like the same one in IdleVerifyCommandArg -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-8115) Add a warning on local node startup if the node is not in Baseline
[ https://issues.apache.org/jira/browse/IGNITE-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Masharov resolved IGNITE-8115. -- Resolution: Duplicate Already done in ignite-8190 > Add a warning on local node startup if the node is not in Baseline > -- > > Key: IGNITE-8115 > URL: https://issues.apache.org/jira/browse/IGNITE-8115 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Philipp Masharov >Priority: Major > Labels: newbie > > The message should contain instructions on how to add the node to baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-8115) Add a warning on local node startup if the node is not in Baseline
[ https://issues.apache.org/jira/browse/IGNITE-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015191#comment-17015191 ] Philipp Masharov commented on IGNITE-8115: -- [http://apache-ignite-developers.2346864.n4.nabble.com/Hint-for-user-that-baseline-topology-should-be-changed-in-order-to-trigger-rebalance-td45023.html] > Add a warning on local node startup if the node is not in Baseline > -- > > Key: IGNITE-8115 > URL: https://issues.apache.org/jira/browse/IGNITE-8115 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Philipp Masharov >Priority: Major > Labels: newbie > > The message should contain instructions on how to add the node to baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-8115) Add a warning on local node startup if the node is not in Baseline
[ https://issues.apache.org/jira/browse/IGNITE-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Masharov reassigned IGNITE-8115: Assignee: Philipp Masharov > Add a warning on local node startup if the node is not in Baseline > -- > > Key: IGNITE-8115 > URL: https://issues.apache.org/jira/browse/IGNITE-8115 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Philipp Masharov >Priority: Major > Labels: newbie > > The message should contain instructions on how to add the node to baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
