[CLOUDSTACK-8043] Have all CloudStack tables's primary keys auto-increment to avoid multi-master DB setup issues

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.6.0
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Rohit Yadav
• Reporter: Rohit Yadav
• Created: 08/Dec/14 09:21
• Updated: 13/Aug/15 12:10
• Resolved: 13/Aug/15 09:52

Description

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