[jira] [Updated] (IGNITE-14709) Allow node to start if there is no bootstraped configuration
[
https://issues.apache.org/jira/browse/IGNITE-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14709:
-
Reviewer: Vyacheslav Koptilin
> Allow node to start if there is no bootstraped configuration
>
>
> Key: IGNITE-14709
> URL: https://issues.apache.org/jira/browse/IGNITE-14709
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently, we faced with a problem when a node starts it is hanged on phase
> when we register {{DistributedConfigurationStorage}}. It happens because when
> {{ConfigurationChanger#register}} is run it requires
> {{ConfigurationStorage#readAll}}, this, in turn, calls
> {{MetaStorageServiceImpl#range}}, but the range is waiting on future until
> cluster init happens, so all process of starting node is hanged.
> Could be reproduced in
> {{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
> A possible solution is to not use metastorage in
> {{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
> keys from Vault.
> Also, node start hangs because {{MetaStorageManager#deployWatches}} also
> waits for metastorage to be initialized with metastorage nodes, so we do not
> need to wait if metastorage nodes weren't explicitly set on start and we
> should move waiting of the future to
> [init|https://issues.apache.org/jira/browse/IGNITE-14414] phase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14709) Allow node to start if there is no bootstraped configuration
[
https://issues.apache.org/jira/browse/IGNITE-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-14709:
-
Description:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
Could be reproduced in
{{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
A possible solution is to not use metastorage in
{{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
keys from Vault.
Also, node start hangs because {{MetaStorageManager#deployWatches}} also waits
for metastorage to be initialized with metastorage nodes, so we do not need to
wait if metastorage nodes weren't explicitly set on start and we should move
waiting of the future to
[init|https://issues.apache.org/jira/browse/IGNITE-14414] phase
was:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
Could be reproduced in
{{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
A possible solution is to not use metastorage in
{{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
keys from Vault.
Also, node start hangs because {{MetaStorageManager#deployWatches}} also waits
for metastorage to be initialized with metastorage nodes, so we do not need to
wait if metastorage nodes weren't explicitly set on start and we should move
that part to [init|https://issues.apache.org/jira/browse/IGNITE-14414] phase
> Allow node to start if there is no bootstraped configuration
>
>
> Key: IGNITE-14709
> URL: https://issues.apache.org/jira/browse/IGNITE-14709
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently, we faced with a problem when a node starts it is hanged on phase
> when we register {{DistributedConfigurationStorage}}. It happens because when
> {{ConfigurationChanger#register}} is run it requires
> {{ConfigurationStorage#readAll}}, this, in turn, calls
> {{MetaStorageServiceImpl#range}}, but the range is waiting on future until
> cluster init happens, so all process of starting node is hanged.
> Could be reproduced in
> {{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
> A possible solution is to not use metastorage in
> {{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
> keys from Vault.
> Also, node start hangs because {{MetaStorageManager#deployWatches}} also
> waits for metastorage to be initialized with metastorage nodes, so we do not
> need to wait if metastorage nodes weren't explicitly set on start and we
> should move waiting of the future to
> [init|https://issues.apache.org/jira/browse/IGNITE-14414] phase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14709) Allow node to start if there is no bootstraped configuration
[
https://issues.apache.org/jira/browse/IGNITE-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-14709:
-
Description:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
Could be reproduced in
{{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
A possible solution is to not use metastorage in
{{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
keys from Vault.
Also, node start hangs because {{MetaStorageManager#deployWatches}} also waits
for metastorage to be initialized with metastorage nodes, so we do not need to
wait if metastorage nodes weren't explicitly set on start and we should move
that part to [init|https://issues.apache.org/jira/browse/IGNITE-14414] phase
was:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
Could be reproduced in
{{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
A possible solution is to not use metastorage in
{{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
keys from Vault.
> Allow node to start if there is no bootstraped configuration
>
>
> Key: IGNITE-14709
> URL: https://issues.apache.org/jira/browse/IGNITE-14709
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently, we faced with a problem when a node starts it is hanged on phase
> when we register {{DistributedConfigurationStorage}}. It happens because when
> {{ConfigurationChanger#register}} is run it requires
> {{ConfigurationStorage#readAll}}, this, in turn, calls
> {{MetaStorageServiceImpl#range}}, but the range is waiting on future until
> cluster init happens, so all process of starting node is hanged.
> Could be reproduced in
> {{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
> A possible solution is to not use metastorage in
> {{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
> keys from Vault.
> Also, node start hangs because {{MetaStorageManager#deployWatches}} also
> waits for metastorage to be initialized with metastorage nodes, so we do not
> need to wait if metastorage nodes weren't explicitly set on start and we
> should move that part to
> [init|https://issues.apache.org/jira/browse/IGNITE-14414] phase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14709) Allow node to start if there is no bootstraped configuration
[
https://issues.apache.org/jira/browse/IGNITE-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-14709:
-
Summary: Allow node to start if there is no bootstraped configuration
(was: Make ConfigurationStorage#readAll async)
> Allow node to start if there is no bootstraped configuration
>
>
> Key: IGNITE-14709
> URL: https://issues.apache.org/jira/browse/IGNITE-14709
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently, we faced with a problem when a node starts it is hanged on phase
> when we register {{DistributedConfigurationStorage}}. It happens because when
> {{ConfigurationChanger#register}} is run it requires
> {{ConfigurationStorage#readAll}}, this, in turn, calls
> {{MetaStorageServiceImpl#range}}, but the range is waiting on future until
> cluster init happens, so all process of starting node is hanged.
> Could be reproduced in
> {{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
> A possible solution is to not use metastorage in
> {{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
> keys from Vault.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
