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

Http Task not Picked soon #376

Open
svelango opened this issue Feb 3, 2025 · 0 comments
Open

Http Task not Picked soon #376

svelango opened this issue Feb 3, 2025 · 0 comments

Comments

@svelango
Copy link

svelango commented Feb 3, 2025

Describe the bug
We are executing 100 Workflows per second in 4 Containers pods with 4 core in each pod. We observe that Http Task is not picked immediately. Updated activeWorkerLastPollTimeout to 2 sec where we saw improvements but not great improvement. Wonder is there any other setting we are missing.

Image

In the above example Task2 is picked after 9 seconds and hence the join took more time.

Details
Conductor version: v3.21.5
Persistence implementation: Cassandra, Postgres, MySQL, Dynomite etc Postgres
Queue implementation: Postgres, MySQL, Dynoqueues etc Postgres
Lock: Redis or Zookeeper?
Workflow definition:
Task definition:
Event handler definition:

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
Http Task pulled immediately and better metrics on pending Http Task Qeueu

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
We are comparing this with AWS Step Functions and this issue is holding us to move forward with Conductor

@svelango svelango changed the title Http Task is Picked Http Task not Picked soon Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant