[
https://issues.apache.org/jira/browse/CLOUDSTACK-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658670#comment-13658670
]
ASF subversion and git services commented on CLOUDSTACK-2486:
-------------------------------------------------------------
Commit 73030f43729f408acd8c6325541db2f184757e80 in branch refs/heads/master
from Prachi Damle <pra...@cloud.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=73030f4 ]
CLOUDSTACK-2486: Deleting the host_details and inserting them back can lead to
mysql deadlock
- Changing the correct details dao. Instead of using separate delete and
insert, we will use ON DUPLICATE KEY UPDATE to avoid the MySQL deadlock
> Deleting the host_details and inserting them back can lead to mysql deadlock
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2486
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2486
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Prachi Damle
> Assignee: Prachi Damle
>
> When host tries to connect to management server, the old host_details are
> deleted and new records are inserted. MySQL deadlock is seen sometimes during
> this delete and insert on the same table. If this error happens, host
> connection fails.
> a) This issue is intermittent issue seen with MySQL. It seems to happen when
> we are deleting and inserting records in the same table in one transaction.
> b)CS auto-corrects this error state:
> CloudStack has host connection 'retry' mechanism where we try to connect back
> to the host. This retry mechanism corrects this issue because the DB issue is
> intermittent and eventually the hosts connect back.
> Hence this does not affect the CS functionality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
