[ 
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. 


  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}}

Possible solution is to not use metastorage in 
{{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg 
keys from Vault. 



> Make ConfigurationStorage#readAll async
> ---------------------------------------
>
>                 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: 10m
>  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)

Reply via email to