Rohit Yadav created CLOUDSTACK-8043:
---------------------------------------
Summary: Have all CloudStack tables's primary keys auto-increment
to avoid multi-master DB setup issues
Key: CLOUDSTACK-8043
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8043
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Rohit Yadav
Fix For: Future, 4.5.0, 4.6.0
In multi-master DB setup, tables where primary keys don't auto-increment can
conflict in case of concurrent insert operations. This was partially fixed in
https://issues.apache.org/jira/browse/CLOUDSTACK-6212
The following tables have a primary key without the auto_increment flag, should
we alter those columns to have auto_increment?
cluster_vsm_map
op_host
op_host_tranfer
op_host_upgrade
op_it_work
op_lock
op_networks
op_router_monitoring_services
op_user_stats_log
user_vm_clone_setting
vm_work_job
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
