lburgazzoli commented on issue #490: Came-k routes takes long time to terminate URL: https://github.com/apache/camel-k/issues/490#issuecomment-466642293 can you try disabling the gc trait? kamel run ... —trait gc.enabled=false ? On Sat, 23 Feb 2019 at 12:49, Kamesh Sampath <notificati...@github.com> wrote: > When developing and deploying camel-k routes with Knative endpoints it > takes a long time to terminate, which is not allowing for quicker redeploys. > > Steps to reproduce: > > 1. Deploy a camel-k route like call "hello.js" > > from("timer?period=3s") > .setBody() > .simple("Hello World") > .to("kantive:channel/hello-world") > > > 1. > > Deploy the route using the command kamel run --dev hello.js > 2. > > CTRL+c to terminate and you will see the deployment pod takes a longer > time to terminate > > The following Knative issue might be one to refer which gives clue that > one of the containers is not sending SIGTERM in a timely way > > Ref: knative/serving#2897 <https://github.com/knative/serving/issues/2897> > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/camel-k/issues/490>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AByEhY3xa2PXjqmROCdiiFEn7pQ_H-Xxks5vQSrfgaJpZM4bN5uZ> > . > -- -- Luca Burgazzoli
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
