[FROG] route-map set metric

Joe Maimon jmaimon at jmaimon.com
Mon Mar 1 21:39:43 UTC 2021


Not surprising. Its a cloud VM with 512Mb ram and 8gb disk, single CPU, 
2gb swapfile.


Quentin Young wrote:
> Somewhat surprised you are seeing 7-8 second runtime as the default 
> number of messages to process before yielding is relatively small at 
> 1000. But yes, lowering that number via zapi-packets is appropriate.
>
> > zebra protocol import route-map is strangely one sided. It would be
> > ever so much more powerful to control both what protocols export to
> > zebra and what they import from zebra, as well as allowing protocols
> > to distinguish the source of the route from zebra
>
> Quite possible I am misunderstanding but it sounds like you're talking 
> about redistribution, e.g.
> https://docs.frrouting.org/en/latest/bgp.html#redistribution
>
> ------------------------------------------------------------------------
> *From:* frog <frog-bounces at lists.frrouting.org> on behalf of Joe 
> Maimon <jmaimon at jmaimon.com>
> *Sent:* Sunday, February 28, 2021 11:45 PM
> *To:* Chriztoffer Hansen <ch at ntrv.dk>
> *Cc:* FRRouting Operator Group - Users List <frog at lists.frrouting.org>
> *Subject:* Re: [FROG] route-map set metric
> External email: Use caution opening links or attachments
>
>
> Joe Maimon wrote:
> > points remain.
> >
> > - BGP full tables loading/kernel-route syncing can easily lock up the
> > processes to the point where they dont respond properly, and more
> > problematic, watchfrr kills them. Rinse, repeat.
> This hidden gem looks like it might work crudely, but effectively.
>
> zebra zapi-packets 250
>
> Initial tests are promising. I can run out of memory on the tiny VM
> before processes lock up or slow thread to death, so far so good.
>
> >
> > In other words, it may not be enough to log SLOW THREAD: task
> > zserv_process_messages (55f1e2bb0750) ran for 7819ms (cpu time 253ms)
> > but actually implement some sort of time based thread yielding right
> > in middle of large batch operations, such as loading 800000 routes 
> or so.
> >
> > - zebra protocol import route-map is strangely one sided. It would be
> > ever so much more powerful to control both what protocols export to
> > zebra and what they import from zebra, as well as allowing protocols
> > to distinguish the source of the route from zebra.
> >
> >
> >
> >
> > _______________________________________________
> > frog mailing list
> > frog at lists.frrouting.org
> > https://lists.frrouting.org/listinfo/frog
> >
> >
>
>
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog




More information about the frog mailing list