Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split with parallelProcessing runs sequentially #3785

Closed
casdtodtenhoefer opened this issue Oct 28, 2022 · 1 comment
Closed

Split with parallelProcessing runs sequentially #3785

casdtodtenhoefer opened this issue Oct 28, 2022 · 1 comment
Labels
kind/question Further information is requested status/stale

Comments

@casdtodtenhoefer
Copy link

casdtodtenhoefer commented Oct 28, 2022

Hello guys,

we encountered a very strange behaviour in our Camel-K integrations. Our body consits of an list with about 10.000 entries and we try to do an parallel split to send them to kafka. In our log we can see, that there are 10 threads, but they are running sequentially. The second thread starts after the first one finishes. We thing that this could be a problem regarding camel-k, because we already have a kind of similar route built with Camel Spring Boot and it's running as intended.

Here are our used routes:

camelRouteBuilder
                    .from("direct:" + getRouteId())
                    .routeId(getRouteId())
                    .split(camelRouteBuilder.body()).streaming().parallelProcessing()
                      .to(getRouteId()+"-send")
                    .end()
                    .to("direct:" + targetRouteName)
            ;

camelRouteBuilder
                .from("direct:" + getRouteId() + "-send")
                .routeId(getRouteId()+"-send")
                .removeHeaders("*")
                .setHeader("kafka.KEY", camelRouteBuilder.simple(getKafkaKey()))
                .to("kafka-producer:{{kafka.topic}}")
                //logging route
                .to("direct:" + getProducerLogging().endpoint)
        ;

Is this a known issue or am I doing something wrong?

Best regards,
Danny

@squakez squakez added the kind/question Further information is requested label Nov 3, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Feb 2, 2023

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Further information is requested status/stale
Projects
None yet
Development

No branches or pull requests

2 participants