Rudder

Bug #7290

Updated by Janos Mattyasovszky almost 8 years ago

Since the hammering was solved in a linked issue, I am modifying the ticket text Is it possible / does is make sense to address tune the issue from maximum number of intentories being processed by the other point: webapp? 

 The uploads are not distributed randomly, there are very big spikes at the same times: After midnight I get a ton of these messages: 

 <pre> 
 rudder:/var/rudder/inventories/accepted-nodes-updates # ll -ltr | gawk '/Dec [2015-10-18 00:14:23] WARN    9/ {print $8}' | sort | uniq -c | sort -n -k1 -r | head -n50 
     900 03:10 
     886 00:05 
     883 01:05 
     715 04:10 
     672 05:15 
     491 02:10 
     408 02:05 
     150 05:16 
     130 04:11 
      88 04:15 
      71 03:11 
      62 05:10 
      53 08:07 
      51 00:00 
      50 10:12 
      42 07:07 
      38 09:12 
      33 06:02 
      30 05:11 
      24 06:15 
      22 11:11 
      22 10:11 
      22 03:05 
      21 11:16 
      20 04:13 
      20 01:08 
      19 07:08 
      19 03:13 
      19 00:08 
      15 01:06 
      14 09:07 
      14 02:08 
      12 03:15 
      11 11:12 
      11 02:06 
      11 01:10 com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Not processing inventory file because there is already the maximum number (50) of inventory waiting 
 to be processed 
 </pre> 

 Regardsless of the splaying of the inventory uploads of the nodes, the relays have a pretty "high" scheduling time, so every batch they upload is a lot, so ~15 minutes after midnight I already have ~450 waiting in the queue...

Back