cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10108) ConfigKey based approach for reading 'ping' configuaration for Management Server
Date Fri, 24 Nov 2017 13:16:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10108:

mrunalinikankariya commented on a change in pull request #2292: CLOUDSTACK-10108:ConfigKey
based approach for reading 'ping' configua…

 File path: engine/schema/src/com/cloud/host/dao/
 @@ -995,8 +994,8 @@ public boolean updateState(Status oldStatus, Event event, Status newStatus,
         if (event.equals(Event.ManagementServerDown)) {
-            Float pingTimeout = NumbersUtil.parseFloat(_configDao.getValue("ping.timeout"),
-            Integer pingInterval = NumbersUtil.parseInt(_configDao.getValue("ping.interval"),
+            float pingTimeout = (Float)_configDepot.get("ping.timeout").value();
 Review comment:
   ConfigKeys can only be defined once so as it is already defined and used in AgentManagerImpl,
it can not be redefined. Also if you check the ConfigKeys, it read the configuration from
ConfigDepot only. 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> ConfigKey based approach for reading 'ping' configuaration for Management Server
> --------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-10108
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: mrunalini
>            Priority: Minor
> In CLOUDSTACK-9886, we are reading ping.interval and ping.timeout using configdao which
involves direct reading of DB. So, replace it with ConfigKey based approach

This message was sent by Atlassian JIRA

View raw message