efaa63a428
bug 10884: try out a global lock instead of per-vm locks
2011-08-01 18:52:06 -07:00
a6a2383561
bug 10929: allow only OperationFailedToError event to trigger transition to Error state.
2011-08-01 18:38:14 -07:00
95d858d1f2
bug 10927: Drop key i_snapshots__removed (if exists) and readd it. Done to fix inconsistency between 2.1.x to 2.2.9 and 2.2.x to 2.2.9 upgrades
2011-08-01 16:22:06 -07:00
a0977ee61f
Fixed db upgrade to do 228 to 229 when do upgrade from 224 branch
2011-08-01 15:44:42 -07:00
b4b87b1de8
bug 10920: avoid deadlocks by avoiding locks on the index on step
2011-08-01 15:32:23 -07:00
f4f51f0451
Revert "bug 10812: modifying dhcp option 119 on domR as per zone config"
...
This reverts commit 606ec843475911680adb743d7975bf7d584ab240.
2011-08-01 13:00:53 -07:00
826a3d6ad0
bug 10812: modifying dhcp option 119 on domR as per zone config
...
status 10812: resolved fixed.
2011-08-01 14:44:31 +05:30
3951699542
bug 10920: convert seconds to milliseconds
2011-07-30 18:19:58 -07:00
6c1cd20fff
Add DB integrity checker, it checks:
...
1. Are there multiple hosts connect to the same local storage pool due to 2.1.x bug
2. Is there any missed premium upgrade
either true answer of above cause mangemnt stopping and asking user to contact Cloud.com support
2011-07-30 17:16:33 -07:00
f49469270e
bug 10920: avoid deadlocks by not using order by random
2011-07-30 12:54:50 -07:00
03fbe13f58
Add upgrade path to 2.2.9
...
Add files
2011-07-29 20:05:50 -07:00
44f3ac98f6
A couple of things:
...
add 229 upgrade path
Bug 10860 - PremiumUpgrade is not run when upgrading to 2.2.8 (edit)
run checker before any components loaded
2011-07-29 20:05:50 -07:00
1c4e1ba5a5
bug 10918: cap async-job execution thread pool to be 2/3 of maximum DB connection limit
2011-07-29 18:33:21 -07:00
d120b9cca4
bug 10770: don't select cluster if it's removed in firstfitplanner
...
status 10770: resolved fixed
2011-07-29 16:37:03 -07:00
41e6aeae96
bug 10884:
...
1. cleanup was scheduled wrong (seconds vs ms)
2. when finding a work item to do, lock one random row to reduce contentions by thundering herds of workers
3. cleanup thread also finds scheduled work items and gets threads to work on them. this way other mgmt servers can take jobs
4. add lots of trace logs
5. commit transactions when returning early
2011-07-29 16:28:06 -07:00
d48e97a368
bug 10768: root cause is StopCommand is not sent out in force stop,
...
status 10768: resolved fixed
2011-07-29 15:41:00 -07:00
c00b9bf5aa
fixed problems with security group. it's possible for threads to disappear due to exceptions. Also it needed to define in memory transaction boundary
2011-07-29 10:41:36 -07:00
1226a49976
bug 10884: use the proper keys this time
2011-07-27 17:58:59 -07:00
9aae53fbb3
Bug 10860 - PremiumUpgrade is not run when upgrading to 2.2.8
...
Use a new target "system-integrity-checker" in components.xml/components-premium.xml.
All checkers must be explicitly specified in XML file, they will execute before any components load
status 10860: resolved fixed
2011-07-27 17:43:38 -07:00
8cc694a579
bug 10884: bump up thread pool and cleanup less often
2011-07-27 14:44:52 -07:00
6fea146903
more index. moved op_lock to memory table to try it
2011-07-27 14:06:40 -07:00
3a8e13f968
Add exception message for AgentManagerImpl.investigate()
2011-07-27 10:52:48 -07:00
7c951361c6
fixed NPE, secondary storage VM host may not exist even the secondary storage VM is running
2011-07-26 17:39:24 -07:00
b116f54741
Generate keystore using RSA rather than DSA
...
Also fix a typo.
2011-07-25 18:23:44 -07:00
200d2b9cd0
bug 10847: sg got executed in a big transaction leading to the deadlock
2011-07-25 17:41:11 -07:00
9c627a15f3
Inaccurate clock new gets an mbean to control it
2011-07-25 16:01:31 -07:00
c610925304
moved agent ping to in memory rather than db based
2011-07-25 15:21:06 -07:00
1b56808be5
brought over agent ping uses the same db connection
2011-07-25 10:57:00 -07:00
10ac7753ed
Switched ping to use the same db connection so that running out of db connections won't affect basic operations
2011-07-25 10:36:00 -07:00
3f18192df8
Make all connections READ COMMITTED isolation level instead of setting it everytime we get the db connection causing useless round trips
2011-07-23 14:58:32 -07:00
7464b6474e
changed a bunch of map logs to trace
2011-07-22 18:12:27 -07:00
12cd5db620
deleted a file by mistake
2011-07-22 11:39:16 -07:00
44ce9488a6
propagate lock table fixes
2011-07-22 11:30:23 -07:00
bb60543fbf
bug 9452: listCapacity - when the hosts > 200 the host_id and storage_pool_id start colliding, to workaround that also compart the capacity type.
2011-07-22 19:56:01 +05:30
bb3d7013a9
bug 9452: ListCapacity - works now. Remove all the pagination logic.
2011-07-22 13:12:44 +05:30
c21273d23a
bug 10734: removed global lock in "DirectAgentScanTimerTask". This lock used to prevent the task from executing on multiple management server simultaniously.
...
status 10734: resolved fixed
2011-07-21 16:18:43 -07:00
ee98887176
2 fixes for Agent Load Balancer:
...
* when management server dies and notifies other management servers about this, the running management server has to cleanup host_transfer records belonging to the died management server
* issue agent load balancing task only when agent load (number of connected agents in the system) exceeds "agent.load.threshold" - 70% by default
Conflicts:
server/src/com/cloud/configuration/Config.java
server/src/com/cloud/host/dao/HostDaoImpl.java
setup/db/db/schema-228to229.sql
2011-07-21 15:28:11 -07:00
d7667180c5
bug 10816: more db lock controls
2011-07-21 13:38:37 -07:00
45074e7cba
bug 10799: There are two problems. The deadlock was ate up but then the savepublicip call return true, causing the problem with the pod_vlan_map hitting a constraint problem. HostPodDao was used as the scope for the insufficient capacity exception which causes the virtualmachinemanager to not to retry starting the vm. It should have been HostPod instead of HostPodDao.
2011-07-21 11:22:55 -07:00
0c91e938e1
bug 10290: Allow turning off router stats collector
...
Status 10290: resolved fixed
2011-07-21 19:52:32 +05:30
1e0c7274ec
bug 10520: CAPACITY_TYPE_PUBLIC_IP and CAPACITY_TYPE_PRIVATE_IP - Change from remove and insert to the to the insert and update model. It doesnt seem like they are referenced for the allocators while creating a vm. Next might change them to calculating them on the fly.
2011-07-21 18:33:47 +05:30
3167c49687
bug 10736: when deploy vm in Basic zone, 1) send vmData/Password info to the Dhcp running in the same pod 2) send dhcp information to all pods in the system only when network.dns.basiczone.updates has "all" value
...
status 10736: resolved fixed
2011-07-20 16:50:58 -07:00
db8be16f98
bug 10632: propagated to 2.2.8.z
2011-07-20 16:11:59 -07:00
06ea7338a8
bug 10732: fix console proxy assignment issue - file was not saved, commit again
2011-07-14 21:56:51 -07:00
1081a3cfaa
bug 10732: fix console proxy assignment issue
2011-07-14 21:56:34 -07:00
18003deedf
bug 10628: root cause is CheckHealthCommand return false, XenServerInvestigator is not called
...
status 10628: resolved fixed
2011-07-14 20:42:26 -07:00
61676ff3ea
Make cluster request timeout to be configurable
2011-07-14 18:11:32 -07:00
d11ac32f08
bug 10727: fixed duplicated usage event generation when create volume from snapshot
...
status 10727: resolved fixed
2011-07-14 10:28:28 -07:00
1a6d859f22
bug 10718: checkSumSync - remove it as we dont require it.
...
status 10718: resolved fixed
2011-07-14 16:48:42 +05:30
b9803a05ae
bug 10705: don't need to print trace
...
status 10705: resolved fixed
2011-07-13 18:35:56 -07:00
Chiradeep Vittal
Kelven Yang
alena
Abhinandan Prateek
frank
Edison Su
anthony
Alex Huang
Sheng Yang
Nitin