sbrueseke commented on issue #13399: URL: https://github.com/apache/cloudstack/issues/13399#issuecomment-5201576868
@DaanHoogland here is the output SELECT * FROM (SELECT id, type, resource_id, created, processed FROM usage_event WHERE type = 'VOLUME.CREATE' ORDER BY id DESC LIMIT 10) sub ORDER BY id ASC; ``` +--------+---------------+-------------+---------------------+-----------+ | id | type | resource_id | created | processed | +--------+---------------+-------------+---------------------+-----------+ | 752179 | VOLUME.CREATE | 1952 | 2026-07-16 14:46:21 | 1 | | 774500 | VOLUME.CREATE | 1956 | 2026-07-23 09:51:20 | 1 | | 775401 | VOLUME.CREATE | 1985 | 2026-07-23 15:42:22 | 1 | | 797749 | VOLUME.CREATE | 1999 | 2026-07-29 11:25:28 | 1 | | 800985 | VOLUME.CREATE | 2000 | 2026-07-30 07:53:38 | 1 | | 817904 | VOLUME.CREATE | 2003 | 2026-08-03 16:22:40 | 1 | | 817927 | VOLUME.CREATE | 2004 | 2026-08-03 16:22:53 | 1 | | 817931 | VOLUME.CREATE | 2005 | 2026-08-03 16:23:05 | 1 | | 817935 | VOLUME.CREATE | 2006 | 2026-08-03 16:23:17 | 1 | | 826827 | VOLUME.CREATE | 2007 | 2026-08-05 09:40:05 | 1 | +--------+---------------+-------------+---------------------+-----------+ ``` I already fixed id 826827 by setting processed to 1 via UPDATE. I sent you a link to the whole Claude conversation. @rp- Is it possible that linstor is involved? The root cause is that usage will do 2 INSERT into the db with the same timestamp. The first INSERT has no vm_id and the second has a vm_id. Is linstor creating the volume first and than is attaching it to the vm and doing it so fast, that it will have the exact same timestamp? This could be an explanation for the 2 INSERT. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
