You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "kiranchavala (via GitHub)" <gi...@apache.org> on 2026/01/07 12:44:53 UTC
[I] Active usage service doesn't poin [cloudstack]
kiranchavala opened a new issue, #12383:
URL: https://github.com/apache/cloudstack/issues/12383
### problem
If there are multiple management server and usage service is running on both the management servers.
If
### versions
ACS 4.20
### The steps to reproduce the bug
Steps to reproduce the issue
1. Have a CloudStack environment (4.20.2) with 2 mgmt servers
2. Have the CloudStack usage service running on both management servers
3. On mgmt 1 , stop the usage service , Check the usage job in the UI
<img width="1614" height="239" alt="Image" src="https://github.com/user-attachments/assets/274b8749-f279-4b5b-88b2-f5d2fc0369d1" />
4. On mgmt 2 , stop the usage service, check the usage job in th UI
It becomes Red N/A
<img width="1607" height="213" alt="Image" src="https://github.com/user-attachments/assets/6b8f6e7e-6493-4951-8672-11789bec1e40" />
5. On mgmt 2 , start the usage service
<img width="1617" height="220" alt="Image" src="https://github.com/user-attachments/assets/a7aef314-da7e-4ab5-ab99-968df325bf18" />
6. It remains in alert state until the usage service is started on mgmt 1
<img width="1627" height="244" alt="Image" src="https://github.com/user-attachments/assets/bde7a491-e3dd-4242-81ff-658d50d647c7" />
Expected behaviour
If the multiple management servers and usage service is running on all the servers then according to the docs, they should coordinate
https://docs.cloudstack.apache.org/en/4.22.0.0/installguide/optional_installation.html#installing-the-usage-server-optional
The Usage Servers will coordinate usage processing. A site that is concerned about availability should install Usage Servers on at least two Management Servers.
### What to do about it?
Usage service running on multiple management server should coordinate
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "Praba-11 (via GitHub)" <gi...@apache.org>.
Praba-11 commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3734255534
Hi, I’d like to work on this issue. I’m planning to look into how the usage service schedules and executes usage processing when multiple management servers are present, and propose a coordination mechanism so jobs don’t fail when one usage service instance is stopped.
Before I start, are there any expected patterns the project prefers (e.g., DB locks, leader election) for coordinating across MS nodes?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland closed issue #12383: No cordination among usage service running on multiple management servers
URL: https://github.com/apache/cloudstack/issues/12383
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "abh1sar (via GitHub)" <gi...@apache.org>.
abh1sar commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3786174102
This is because Usage-server-2 doesn't take over the processing from Usage-server-1 if Usage-server-1 is shutdown gracefully.
When usage-server-1 shuts down gracefully, the AbandonJob shutdown hook deletes all the open jobs. When usage-server-2 runs its heartbeat, getNextRecurringJob() returns null (job was deleted), so no takeover occurs.
In case of an abrupt shutdown, the open Job owned by Usage-server-1 would still be existing. Heartbeat check from usage-server-2 would have takeover 5 mins after the heartbeat in the last undeleted job.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3737216224
@Praba-11 , first of all thank you for chipping in. The usage is an (kind of) off-line batch job that runs daily. Ideally It would be able to run and create usage data for specific intervals and usage types. The most important part is that the “owner” of the job will run the usage job for the latest period, and that would hopefully mean the last 24hrs. Taking over a job should never need to happen, but if you think some kind of leader election could benefit the processing, feel free to propose.
If you want to make use of DB locks you are in for a big job. This would only make sense when processing would not be done on the basis of the whole event set, but on a per account or even a per entity basis.
please report back whether you finish the job or not, so we know the state of the issue? thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3758626908
@Praba-11 @kiranchavala feel free to add issues for both the UI clarity and a different (more direct) way of picking up the unprocessed job. At this moment it may take up to a day before the backup server notices it can do any work, which is by design. I am closing this issue n the meanwhile.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "kiranchavala (via GitHub)" <gi...@apache.org>.
kiranchavala commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3782897080
Reopening this as I believe this issue exists and is cricital for users using the usage service on multiple management servers
https://docs.cloudstack.apache.org/en/4.22.0.0/installguide/optional_installation.html#installing-the-usage-server-optional
Steps to reproduce the issue
1. Have a CloudStack environment (4.20.2 / 4.22) with 2 mgmt servers (mgmt1 and mgmt2)
2. Have the CloudStack usage service running on both management servers
```
[root@ref-trl-10682-k-Mol8-kiran-chavala-mgmt1 ~]# service cloudstack-usage status
Redirecting to /bin/systemctl status cloudstack-usage.service
● cloudstack-usage.service - CloudStack Usage Server
Loaded: loaded (/usr/lib/systemd/system/cloudstack-usage.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2026-01-22 04:49:14 UTC; 1h 52min ago
Docs: http://www.cloudstack.org/
Process: 11161 ExecStartPre=/usr/share/cloudstack-common/scripts/installer/pre-check.sh (code=exited, status=0/SUCCESS)
Main PID: 11184 (java)
Tasks: 27 (limit: 31267)
Memory: 440.8M
CGroup: /system.slice/cloudstack-usage.service
└─11184 /usr/bin/java -Dpid=11184 -Xms256m -Xmx2048m --add-opens=java.base/java.lang=ALL-UNNAMED -cp /usr/share/cloudstack-usage/*:/usr/share/cloudstack-usage/lib/*:/usr/share/c>
Jan 22 04:49:14 ref-trl-10682-k-Mol8-kiran-chavala-mgmt1 systemd[1]: Starting CloudStack Usage Server...
Jan 22 04:49:14 ref-trl-10682-k-Mol8-kiran-chavala-mgmt1 systemd[1]: Started CloudStack Usage Server.
[root@ref-trl-10682-k-Mol8-kiran-chavala-mgmt2 ~]# service cloudstack-usage status
Redirecting to /bin/systemctl status cloudstack-usage.service
● cloudstack-usage.service - CloudStack Usage Server
Loaded: loaded (/usr/lib/systemd/system/cloudstack-usage.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2026-01-22 04:49:12 UTC; 1h 52min ago
Docs: http://www.cloudstack.org/
Process: 7839 ExecStartPre=/usr/share/cloudstack-common/scripts/installer/pre-check.sh (code=exited, status=0/SUCCESS)
Main PID: 7862 (java)
Tasks: 26 (limit: 31267)
Memory: 509.7M
CGroup: /system.slice/cloudstack-usage.service
└─7862 /usr/bin/java -Dpid=7862 -Xms256m -Xmx2048m --add-opens=java.base/java.lang=ALL-UNNAMED -cp /usr/share/cloudstack-usage/*:/usr/share/cloudstack-usage/lib/*:/usr/share/clo>
Jan 22 04:49:12 ref-trl-10682-k-Mol8-kiran-chavala-mgmt2 systemd[1]: Starting CloudStack Usage Server...
Jan 22 04:49:12 ref-trl-10682-k-Mol8-kiran-chavala-mgmt2 systemd[1]: Started CloudStack Usage Server.
```
```
mysql> select * from usage_job;
+----+-----------------------------------------------------+-------+----------+-----------+--------------+------------+-----------+------------+----------+---------+---------------------+
| id | host | pid | job_type | scheduled | start_millis | end_millis | exec_time | start_date | end_date | success | heartbeat |
+----+-----------------------------------------------------+-------+----------+-----------+--------------+------------+-----------+------------+----------+---------+---------------------+
| 3 | ref-trl-10682-k-Mol8-kiran-chavala-mgmt1/10.0.34.29 | 25630 | 0 | 0 | 0 | 0 | 0 | NULL | NULL | NULL | 2026-01-22 06:50:01 |
+----+-----------------------------------------------------+-------+----------+-----------+--------------+------------+-----------+------------+----------+---------+---------------------+
1 row in set (0.00 sec)
```
3. Change the global setting
```
usage.stats.job.aggregation.range to 5
usage.stats.job.exec.time to an upcoming timestamp 07:00
```
4. Restart the cloudstack usage service on both management servers
service cloudstack-usage restart
Check the usage log on both the management servers , the following message should be present saying the usage service will run at 07:00
```
2026-01-22 06:48:46,854 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_6ced2e17] (main:[]) (logid:) Usage is configured to execute in time zone [UTC], at [07:00], each [5] minutes; the current time in that timezone is [2026-01-22T06:48:46+0000] and the next job is scheduled to execute at [2026-01-22T07:00:00+0000]. During its execution, Usage will aggregate stats according to the time zone [GMT] defined in global setting [usage.aggregation.timezone].
2026-01-22 06:48:58,062 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_6ced2e17] (main:[]) (logid:) Usage is configured to execute in time zone [UTC], at [07:00], each [5] minutes; the current time in that timezone is [2026-01-22T06:48:58+0000] and the next job is scheduled to execute at [2026-01-22T07:00:00+0000]. During its execution, Usage will aggregate stats according to the time zone [GMT] defined in global setting [usage.aggregation.timezone].
```
4. Deploy a vm or perform some activities on cloudstack so that usage events are generated
5. Stop the cloudstack-usage service on mgmt1
service cloudstack-usage stop
usage logs on mgmt1 says it have removed the entry in the database
```
2026-01-22 06:57:04,335 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_6ced2e17] (Thread-0:[]) (logid:) exiting Usage Manager
2026-01-22 06:57:04,349 INFO [usage.dao.UsageJobDaoImpl_EnhancerByCloudStack_cb74c9ff] (Thread-0:[]) (logid:) Found 1 opens job, to remove
2026-01-22 06:57:04,349 DEBUG [usage.dao.UsageJobDaoImpl_EnhancerByCloudStack_cb74c9ff] (Thread-0:[]) (logid:) Removing job - id: 3, pid: 25630, job type: 0, scheduled: 0, heartbeat: 2026-01-22T06:57:01.000+0000
```
Check the db
```
mysql> select * from usage_job;
Empty set (0.00 sec)
```
Check the Check the usage status on the UI , it says last successful job 56 yrs ago
<img width="1605" height="659" alt="Image" src="https://github.com/user-attachments/assets/e2fda535-c6db-4c11-bad4-269d837f90fb" />
6. At 07:00 check the usage ogs on mgmt2
```
2026-01-22 07:00:00,001 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_6ced2e17] (Usage-Job-1:[]) (logid:) starting usage job...
2026-01-22 07:00:00,006 DEBUG [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_6ced2e17] (Usage-Job-1:[]) (logid:) Not owner of usage job, skipping...
2026-01-22 07:00:00,006 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_6ced2e17] (Usage-Job-1:[]) (logid:) usage job complete
```
7. I have also waited for 24 hrs a, and the cross checked if usage service on mgmt2 picks up the job
Reference log snippets
```
2026-01-19 11:57:00,002 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) starting usage job... 2026-01-19 11:57:00,006 DEBUG [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) Not owner of usage job, skipping... 2026-01-19 11:57:00,006 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) usage job complet
2026-01-20 11:52:00,003 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) usage job complete
2026-01-20 11:57:00,000 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) starting usage job...
2026-01-20 11:57:00,003 DEBUG [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) Not owner of usage job, skipping...
2026-01-20 11:57:00,003 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) usage job complete
```
Workaround
Only when then usage service is started on management server 1 , it starts to process the usage jobs
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "Praba-11 (via GitHub)" <gi...@apache.org>.
Praba-11 commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3756579319
@DaanHoogland, Thanks for the clarification and for running the scenario.
Based on your explanation, it looks like the usage job coordination is already functioning correctly, and the red/green indicator only reflects whether the local MS has a usage service running, not the global job ownership or execution state.
So the confusion seems to be around UI feedback rather than backend coordination. I’ll step back from proposing coordination changes here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3719615873
This is how usage works:
- if one starts it claims the job
- if the second starts it refuses to claim the job
- if the first stops and reliquishes the job, nothing happens until
- a usage server wakes up and checks if there is a claimed job.
@kiranchavala, how did you stop the usage server?
Did you check the job records in the DB?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3728780639
Sorry @kiranchavala , but you have not convinced me yet, I will replay your scenario.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3738486178
@kiranchavala , I ran your scenario and the job is coordinated between the server that is running and the one that is stopped, the red bullit point is there indeed but that does not mean the job is not taken over. The red (or green) bullit only says whether the MS you are connected to has a usage server running locally. I think this is not very useful functionality.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "abh1sar (via GitHub)" <gi...@apache.org>.
abh1sar commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3783016114
Will check it out
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "kiranchavala (via GitHub)" <gi...@apache.org>.
kiranchavala commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3728594506
@DaanHoogland Thanks for the usage service logic
Please find the steps that I followed
1. Have a CloudStack environment (4.20.2) with 2 mgmt servers (mgmt1 and mgmt2)
2. Have the CloudStack usage service running on both management servers
3. Change the global setting
usage.stats.job.aggregation.range to 5
usage.stats.job.exec.time to an upcoming timestamp
Restart the cloudstack usage service
Check the usage log on both the management servers , the following message should be present
```
2026-01-09 08:56:44,369 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (main:[]) (logid:) Usage is configured to execute in time zone [UTC], at [09:00], each [5] minutes; the current time in that timezone is [2026-01-09T08:56:44+0000] and the next job is scheduled to execute at [2026-01-09T09:00:00+0000]. During its execution, Usage will aggregate stats according to the time zone [GMT] defined in global setting [usage.aggregation.timezone].
```
4. Stop the cloudstack-usage service on mgmt1
```
service cloudstack-usage stop
[root@ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 ~]# service cloudstack-usage status
Redirecting to /bin/systemctl status cloudstack-usage.service
● cloudstack-usage.service - CloudStack Usage Server
Loaded: loaded (/usr/lib/systemd/system/cloudstack-usage.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2026-01-09 08:58:14 UTC; 2h 51min ago
Docs: http://www.cloudstack.org/
Process: 3822 ExecStart=/bin/sh -ec /usr/bin/java -Dpid=${JAVA_PID} $JAVA_OPTS $JAVA_DEBUG -cp $CLASSPATH $JAVA_CLASS (code=exited, status=143)
Main PID: 3822 (code=exited, status=143)
Jan 09 08:56:30 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: cloudstack-usage.service: Main process exited, code=exited, status=143/n/a
Jan 09 08:56:30 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: cloudstack-usage.service: Failed with result 'exit-code'.
Jan 09 08:56:30 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: Stopped CloudStack Usage Server.
Jan 09 08:56:30 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: Started CloudStack Usage Server.
Jan 09 08:58:14 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: Stopping CloudStack Usage Server...
Jan 09 08:58:14 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: cloudstack-usage.service: Main process exited, code=exited, status=143/n/a
Jan 09 08:58:14 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: cloudstack-usage.service: Failed with result 'exit-code'.
Jan 09 08:58:14 ref-trl-10556-k-Mol8-kiran-chavala-mgmt1 systemd[1]: Stopped CloudStack Usage Server.
```
Check the usage status on the UI
<img width="1678" height="314" alt="Image" src="https://github.com/user-attachments/assets/73e9b569-75ab-41aa-8491-f76c2308529a" />
5. Usage log on mgmt 1
```
2026-01-09 08:58:14,188 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Thread-0:[]) (logid:) exiting Usage Manager
2026-01-09 08:58:14,195 INFO [usage.dao.UsageJobDaoImpl_EnhancerByCloudStack_ae7858fa] (Thread-0:[]) (logid:) Found 1 opens job, to remove
2026-01-09 08:58:14,195 DEBUG [usage.dao.UsageJobDaoImpl_EnhancerByCloudStack_ae7858fa] (Thread-0:[]) (logid:) Removing job - id: 5, pid: 3822, job type: 0, scheduled: 0, heartbeat: 2026-01-09T08:57:59.000+0000
``
6. Usage log om mgm2
```
2026-01-09 09:00:00,002 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) starting usage job...
2026-01-09 09:00:00,006 DEBUG [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) Not owner of usage job, skipping...
2026-01-09 09:00:00,007 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) usage job complete
2026-01-09 09:05:00,001 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) starting usage job...
2026-01-09 09:05:00,004 DEBUG [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) Not owner of usage job, skipping...
2026-01-09 09:05:00,004 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) usage job complete
2026-01-09 09:10:00,001 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) starting usage job...
2026-01-09 09:10:00,004 DEBUG [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) Not owner of usage job, skipping...
2026-01-09 09:10:00,005 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) usage job complete
2026-01-09 09:15:00,001 INFO [cloud.usage.UsageManagerImpl_EnhancerByCloudStack_4ff0bd12] (Usage-Job-1:[]) (logid:) starting usage job...
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland closed issue #12383: No cordination among usage service running on multiple management servers
URL: https://github.com/apache/cloudstack/issues/12383
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] No cordination among usage service running on multiple management servers [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12383:
URL: https://github.com/apache/cloudstack/issues/12383#issuecomment-3811735996
fixed in #12507
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org