With this increasing capacity of processing AMI sets with hundred of thousands of ADOs (future ones and past ones) an AMI log can grow to sizes that were unexpected to me. I just had one of 276 Mbytes in my hands (well ... not my hands really, don't print your logs please!)
I need a Delete Log controller. Access control Is easy but because these ones are written at absurd fast speeds by monolog I can see a race condition where deletion might just make a file unavailable while logging and all fails. So I will also add a restriction that only allows deletion IF the queues are empty.
What?
With this increasing capacity of processing AMI sets with hundred of thousands of ADOs (future ones and past ones) an AMI log can grow to sizes that were unexpected to me. I just had one of 276 Mbytes in my hands (well ... not my hands really, don't print your logs please!)
I need a Delete Log controller. Access control Is easy but because these ones are written at absurd fast speeds by monolog I can see a race condition where deletion might just make a file unavailable while logging and all fails. So I will also add a restriction that only allows deletion IF the queues are empty.
@alliomeria just stuff to discuss