* Olivier Benghozi <olivier.bengh...@wifirst.fr> [2018-12-21 02:05]: > PR1270686 > > restart statistics-service
This PR is one example of something I don't like in most Juniper PRs. It states the command you quoted but then there is also this text: Workaround: Disable pfed's periodic refresh using config: set accounting-options periodic-refresh disable Nowhere in this PR is explained what that does and what possible side-effects are. You only find this exact command in a post on the Juniper forums: > set accounting-options periodic-refresh disable > -->Periodic-refresh is disabled to change the default behavior for > stats collection. Pre-BBE, stats were constantly collected in JUNOS. > This uses CPU cycles that are needed for call set up. > -->With the introduction of BBE in JUNOS, we needed to change the > behavior for stats to be on demand. That is what disabling > periodic-refresh does. There is no negative impact to accurate stats > or interim stats. > -->Without this disabled, accounting will be very inefficient and not > scale. This might be the correct explanation or it might be just a text from someone who wants to gain "kudos" so that he can get to the next level in the Juniper Support pantheon aka "The Stack Exchange disease". Either way it would be very nice if Juniper would post some more information on *what* a workaround does and when it would not be wise to use it. In this case you should probably not use the workaround if you have a scaled BBE setup I would imagine. Regards Sebastian -- GPG Key: 0x58A2D94A93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp