[jira] [Updated] (IGNITE-9561) Optimize affinity initialization for started cache groups
[
https://issues.apache.org/jira/browse/IGNITE-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko updated IGNITE-9561:
Fix Version/s: (was: 2.7)
2.8
> Optimize affinity initialization for started cache groups
> -
>
> Key: IGNITE-9561
> URL: https://issues.apache.org/jira/browse/IGNITE-9561
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.8
>
>
> At the end of
> {noformat}
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager#processCacheStartRequests
>
> {noformat}
> method we're initializing affinity for cache groups starting at current
> exchange.
> We do it one-by-one and synchronously wait for AffinityFetchResponse for each
> of the starting groups. This is inefficient. We may parallelize this process
> and speed up caches starting process.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9561) Optimize affinity initialization for started cache groups
[
https://issues.apache.org/jira/browse/IGNITE-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko updated IGNITE-9561:
Description:
At the end of
{noformat}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager#processCacheStartRequests
{noformat}
method we're initializing affinity for cache groups starting at current
exchange.
We do it one-by-one and synchronously wait for AffinityFetchResponse for each
of the starting groups. This is inefficient. We may parallelize this process
and speed up caches starting process.
NOTE: There are also a lot of affinity recalculation methods in:
{noformat}
CacheAffinitySharedManager
{noformat}
which all looks like iterate over cache groups and recalculate affinity for all
of them. We can easily speed-up each of such methods executing in parallel
affinity re-calculation for each of cache groups.
was:
At the end of
{noformat}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager#processCacheStartRequests
{noformat}
method we're initializing affinity for cache groups starting at current
exchange.
We do it one-by-one and synchronously wait for AffinityFetchResponse for each
of the starting groups. This is inefficient. We may parallelize this process
and speed up caches starting process.
NOTE: There are also a lot of affinity recalculation methods in:
{noformat}
CacheAffinitySharedManager
{noformat}
which all looks like iterate over cache groups and recalculate affinity for all
of them. We can easily parallelize each of such methods executing in parallel
affinity re-calculation for each of cache group.
> Optimize affinity initialization for started cache groups
> -
>
> Key: IGNITE-9561
> URL: https://issues.apache.org/jira/browse/IGNITE-9561
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.8
>
>
> At the end of
> {noformat}
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager#processCacheStartRequests
>
> {noformat}
> method we're initializing affinity for cache groups starting at current
> exchange.
> We do it one-by-one and synchronously wait for AffinityFetchResponse for each
> of the starting groups. This is inefficient. We may parallelize this process
> and speed up caches starting process.
> NOTE: There are also a lot of affinity recalculation methods in:
> {noformat}
> CacheAffinitySharedManager
> {noformat}
> which all looks like iterate over cache groups and recalculate affinity for
> all of them. We can easily speed-up each of such methods executing in
> parallel affinity re-calculation for each of cache groups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9561) Optimize affinity initialization for started cache groups
[
https://issues.apache.org/jira/browse/IGNITE-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko updated IGNITE-9561:
Description:
At the end of
{noformat}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager#processCacheStartRequests
{noformat}
method we're initializing affinity for cache groups starting at current
exchange.
We do it one-by-one and synchronously wait for AffinityFetchResponse for each
of the starting groups. This is inefficient. We may parallelize this process
and speed up caches starting process.
NOTE: There are also a lot of affinity recalculation methods in:
{noformat}
CacheAffinitySharedManager
{noformat}
which all looks like iterate over cache groups and recalculate affinity for all
of them. We can easily parallelize each of such methods executing in parallel
affinity re-calculation for each of cache group.
was:
At the end of
{noformat}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager#processCacheStartRequests
{noformat}
method we're initializing affinity for cache groups starting at current
exchange.
We do it one-by-one and synchronously wait for AffinityFetchResponse for each
of the starting groups. This is inefficient. We may parallelize this process
and speed up caches starting process.
> Optimize affinity initialization for started cache groups
> -
>
> Key: IGNITE-9561
> URL: https://issues.apache.org/jira/browse/IGNITE-9561
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.8
>
>
> At the end of
> {noformat}
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager#processCacheStartRequests
>
> {noformat}
> method we're initializing affinity for cache groups starting at current
> exchange.
> We do it one-by-one and synchronously wait for AffinityFetchResponse for each
> of the starting groups. This is inefficient. We may parallelize this process
> and speed up caches starting process.
> NOTE: There are also a lot of affinity recalculation methods in:
> {noformat}
> CacheAffinitySharedManager
> {noformat}
> which all looks like iterate over cache groups and recalculate affinity for
> all of them. We can easily parallelize each of such methods executing in
> parallel affinity re-calculation for each of cache group.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
