[
https://issues.apache.org/jira/browse/CLOUDSTACK-9886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312515#comment-16312515
]
ASF subversion and git services commented on CLOUDSTACK-9886:
-------------------------------------------------------------
Commit ebb7a5279d0bf5d538081e6ec34fa46d76d40b8f in cloudstack's branch
refs/heads/master from mrunalinikankariya
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=ebb7a52 ]
CLOUDSTACK-10108: ConfigKey based approach for reading 'ping' configuaration
(#2292)
In CLOUDSTACK-9886, we are reading ping.interval and ping.timeout using
configdao which involves direct reading of DB. So, replaced it with ConfigKey
based approach.
> After restarting cloudstack-management , It takes time to connect hosts
> -----------------------------------------------------------------------
>
> Key: CLOUDSTACK-9886
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9886
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: mrunalini
>
> More the value of 'ping.interval' and 'ping.timeout' , more the time taken
> for host reconnection after management server restart.
> Solution : There is a timer task which connect to host based on values from
> ping timeout and ping interval.
> (System.currentTimeMillis() >> 10) - (ping.timeout * ping.interval)
> So if this values are large, host will not be connected immediately after
> restart.
> After management server restart, host should be connected irrespective of
> ping intervals.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
