Bug #184
host_shares table imbroglio
| Status: | Closed | Start date: | 12/22/2009 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - | |||
| Resolution: | wontfix | Pull request: | ||
| Affected Versions: | 
Description
After some running months the host_share table of one.db seems to be in a clutter:
1. Some cpu_usage are only '1', some '200' (Could be caused by the migration from 1.2 to 1.4!)
2. Some values are negative on mem_usage and cpu_usage. I was so before the migration
3. Some machines have no vm, but used_cpu still greater as 0.
The hosts who have negative or false values are not been used! 
From my 12 Hosts, only 7 or so are beeing used be one, massively - We have up to 30 VMs running in a good day - While 5 hosts are not being allocated at all.
abatesting:~# sqlite3 /var/lib/one/one.db 'select * from host_shares ORDER BY used_mem,mem_usage,cpu_usage ASC;'
43|0|4117504|1|0|16474212|400|0|12168272|398|0|4117504|2|1                                                      
39|0|979966|300|0|16474212|400|0|16347148|398|0|4772704|1|1                                                     
41|0|-2087940|-100|0|16474212|400|0|16339404|399|0|5033828|0|0                                                  
38|0|0|0|0|16474212|400|0|16342740|399|0|5065988|0|0                                                            
34|0|-4186115|100|0|16474212|400|0|16342808|400|0|5633624|0|0                                                   
31|0|-2092034|100|0|16474212|400|0|16345488|399|0|5763180|0|0                                                   
37|0|0|0|0|16474212|400|0|16347624|398|0|5813816|1|0                                                            
36|0|4094|200|0|16474212|400|0|16348492|399|0|6613448|0|0                                                       
32|0|6141|0|0|16474212|400|0|16342392|400|0|7533456|0|0                                                         
35|0|0|0|0|16474212|400|0|16324944|400|0|9094136|0|0
42|0|7189504|300|0|16474212|400|0|8881012|286|0|16388152|113|2
30|0|10331136|300|0|16474212|400|0|5709844|207|0|16389920|192|3
abatesting:~# onevm list
  ID     USER     NAME STAT CPU     MEM        HOSTNAME        TIME
2531     root 2003_DE3 runn   0 2096128      172.22.0.2 22 00:14:34
2694     root hardy-x6 runn   0 4117504     172.22.0.13 10 21:20:36
2720     root 200332DE dele   0 3072000      172.22.0.2 08 00:31:56
2743     root 200332DE runn   0 3072000      172.22.0.3 06 20:38:47
2793     root win764DE runn   0 4117504      172.22.0.2 00 19:53:27
2818     root win764DE runn   0 4117504      172.22.0.2 00 01:20:09
2819     root Tvista64 runn   0 4117504      172.22.0.3 00 00:27:36
History
#1
     Updated by Ignacio M. Llorente over 11 years ago
    Updated by Ignacio M. Llorente over 11 years ago
    - Target version changed from Release 1.4 to Release 1.4.2
#2
     Updated by Ruben S. Montero over 10 years ago
    Updated by Ruben S. Montero over 10 years ago
    - Status changed from New to Closed
- Target version deleted (Release 1.4.2)
- Resolution set to wontfix
This is probably because of a 1.2 to 1.4 migration, and some bugs identify in the Host Manager component. I am closing this and address future issues in separate tickets