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.

Sign up for GitHub

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

Jump to bottom

Setting parallelism to COEFFICIENT 1 thrashes #1297

Closed
sjezewski opened this issue Jan 31, 2017 · 1 comment
Closed

Setting parallelism to COEFFICIENT 1 thrashes #1297

sjezewski opened this issue Jan 31, 2017 · 1 comment

Comments

@sjezewski
Copy link
Contributor

I'm working on the farday poc (test 4) when I ran across this bug. Chatting w Matt I think we saw this w xumak as well.

Basically I have a pipeline w parallelism set to COEFFICIENT and 1. When I create this pipeline (after the input repo exists w a single commit w a large amount of data), pachyderm goes nuts.

  • we see the pipeline from pachctl list-pipeline
  • we don't see any jobs listed from pachctl list-job
  • kubectl get all shows no job pods

But ... doing pachctl list-commit -a pipelines_output_repo shows ~10 new commits / second. They are all unfinished.

Changing the pipeline spec to CONSTANT fixes this problem.
@sjezewski sjezewski added the bug label Jan 31, 2017
@sjezewski sjezewski added this to the v1.4 milestone Jan 31, 2017
@sjezewski sjezewski modified the milestone: v1.4 May 24, 2017
@sjezewski sjezewski removed the bug label Oct 18, 2017
@sjezewski
Copy link
Contributor Author

stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sjezewski