Timur Aitov
Timur Aitov
@Tuetuopay Hi! Look at this PR, please
Yes, i see your #2804. And our changes conflict :) My changes are only in the correct index generation in binary format (with test coverage). Which should be much faster...
> How about the output of peers not in a peer group? ``` $ ./gobgp neig Peer Group AS Up/Down State |#Received Accepted 127.0.2.1 group1 12345 18d 23:31:55 Establ |...
> I don't think it's a good idea for GoBGP's most core code to have two different implementations. What's the maximum buffer size of Go's buffered channel? If it's large,...
Сonfiguration example: ``` peer-groups: - config: peer-group-name: group1 peer-as: 12345 local-as: 54321 incoming-channel-timeout: 1 incoming-channel: channel-type: buffer size: 64 outgoing-channel: channel-type: buffer size: 64 neighbors: - config: neighbor-address: 10.0.0.1 peer-group:...
> btw, what kind of use case do you have that puts such a heavy load on GoBGP? Paths are being cyclically updated from peers due to attribute updates. And...
@fujita gentle ping
@fujita gentle ping
> Why just not removing incoming queues? - Then peers can start flap (hold timer expired). - OOM on remote peer (overflow outgoing fsm channel).