search

skupperproject / skupper

Skupper is an implementation of a Virtual Application Network, enabling rich hybrid cloud communication.
http://skupper.io
Apache License 2.0
592 stars 74 forks source link

Exposing a large number of services (> 300) #915

Open jeinwag opened 2 years ago

jeinwag commented 2 years ago

I'm currently trying to run skupper with a rather large number of services (355 to be precise).

I annotated all services accordingly, but only 75 were created in the remote cluster.

Then I started another attempt, annotating the services in smaller batches of 10 with a minute wait time between each batch. This time I got 188 services in the remote cluster.

The router wrote the message Link blocked with zero credit for 16 seconds.

Are there any tweaks I can apply or is 350 services just too many?

ted-ross commented 2 years ago

This is a bug we need to look into. You should be able to run way more than 355 services. I suspect that the problem is with the automatic service-sync.

On Mon, Oct 17, 2022 at 7:25 AM Julian Einwag @.***> wrote:

I'm currently trying to run skupper with a rather large number of services (355 to be precise).

I annotated all services accordingly, but only 75 were created in the remote cluster.

Then I started another attempt, annotating the services in smaller batches of 10 with a minute wait time between each batch. This time I got 188 services in the remote cluster.

The router wrote the message Link blocked with zero credit for 16 seconds.

Are there any tweaks I can apply or is 350 services just too many?

— Reply to this email directly, view it on GitHub https://github.com/skupperproject/skupper/issues/915, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFEKJR657THL6QHKRGCTKTWDUZTLANCNFSM6AAAAAARG664CI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

jeinwag commented 2 years ago

This is a bug we need to look into. You should be able to run way more than 355 services.

Good to hear!

Btw, by now the number of services in the remote cluster has gone up to 354. But it took very long, I guess more than two hours.

skupper network status also takes a very long time.