[
https://issues.apache.org/jira/browse/CLOUDSTACK-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258793#comment-16258793
]
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…
URL: https://github.com/apache/cloudstack/pull/2292#discussion_r151899301
##########
File path: engine/schema/src/com/cloud/host/dao/HostDaoImpl.java
##########
@@ -995,8 +994,8 @@ public boolean updateState(Status oldStatus, Event event,
Status newStatus, Host
}
}
if (event.equals(Event.ManagementServerDown)) {
- Float pingTimeout =
NumbersUtil.parseFloat(_configDao.getValue("ping.timeout"), 2.5f);
- Integer pingInterval =
NumbersUtil.parseInt(_configDao.getValue("ping.interval"), 60);
+ float pingTimeout =
(Float)_configDepot.get("ping.timeout").value();
Review comment:
ConfigKey for ping.timeout and ping.interval is already defined in
AgentManagerImpl. As per my understanding ConfigDepot cached all the
configuration parameters so i am reading from configDepot.
----------------------------------------------------------------
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:
us...@infra.apache.org
> ConfigKey based approach for reading 'ping' configuaration for Management
> Server
> --------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10108
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10108
> 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
(v6.4.14#64029)
