search

dmwm / CMSRucio

7 stars 31 forks source link

make a prototype of the rucio hermes to study message Queue #355 #369

Closed ericvaandering closed 1 year ago

yuyiguo commented 2 years ago

created the first PR to debug hermes upgrade stopm.py to the current version made a new SC8 VM, loaded with podman and other required tools/libraries. Built test images that are running on rucio int. Examined hermes daemon log files. learning/studing hermes code.

yuyiguo commented 1 year ago

Successfully made the rucio messages table filled with data and Hermes can send messages to AMQ broker 500HZ and beyond. We tested on rucio int with 500HZ. The average production Kronos traces is below 20HZ and occasionally peak is way below 500HZ, mostly around 100HZ. The average production of rucio events is about the same as the Kronos. It may be slightly higher than Kronos sometimes, but it is way below the 500HZ.

During the study, we did not find any problem in the test broker cms-test-mb.cern.ch. It was able to handle 500HZ receiving for days and showed no concern. In the test broker, we did not have a sending set up for the Hermes/events topic, but we examined Kronos both receiving/sending messages when there were peaks, it show no problems at all.

Weare done with the prototype and will discuss what we found in the related ticket.

klannon commented 1 year ago

I can't understand what aspect of Rucio this issue targets. @yuyiguo and/or @ericvaandering can you set the "Dev Priority" field in the project board to help me keep this straight?

yuyiguo commented 1 year ago

@klannon This ticket is closed. I tried to add the "Dev Priority" on it but did not find a proper label from the list and I could not add a new one (AMQ). I used "Rucio core".