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

SCDF 2.11.0-RC1 composed task runner documentation #5441

Closed
vauvenal5 opened this issue Aug 28, 2023 · 7 comments
Closed

SCDF 2.11.0-RC1 composed task runner documentation #5441

vauvenal5 opened this issue Aug 28, 2023 · 7 comments
Milestone

Comments

@vauvenal5
Copy link

Problem description:
When I start a composed task containing boot 3 / batch 5 tasks. The composed task is stuck after the first task. I believe this is due to the composed task runner itself being started with schema-target boot2. However, I was not able to find any documentation on how to configure the composed task runner properly.

Solution description:
Can you provide an example or better documentation on how the composed task runner is to be user in context of boot 3 / batch 5 tasks?

@github-actions github-actions bot added the status/need-triage Team needs to triage and take a first look label Aug 28, 2023
@onobc onobc added this to the 2.11.0 milestone Aug 29, 2023
@cppwfs
Copy link
Contributor

cppwfs commented Sep 5, 2023

Can you verify that the SCDF 2.11.0-RC1 is running CTR 2.11.0-RC1?

@cppwfs cppwfs added status/need-feedback Calling participant to provide feedback and removed status/need-triage Team needs to triage and take a first look labels Sep 5, 2023
@klopfdreh
Copy link
Contributor

You can see the schema when ever a task is launched - in the intended column for this.

We had issues with a stuck CTR when we switched to entry point boot instead of entry point shell.

can you have a look if you have two entries for the CTR in the UI?

@cppwfs
Copy link
Contributor

cppwfs commented Sep 12, 2023

There are no doc changes required for the creation or execution of CTR. However, for app registration, you must choose the correct boot version for the application. I'll add a note mentioning this.

One question, did the first task start and complete successfully?

@vauvenal5
Copy link
Author

Hi. Sorry I am currently on vacation. I will respond to everything at the end of the month.

@github-actions github-actions bot added for/team-attention For team attention and removed status/need-feedback Calling participant to provide feedback labels Sep 12, 2023
@onobc onobc removed the for/team-attention For team attention label Sep 13, 2023
@onobc
Copy link
Contributor

onobc commented Sep 13, 2023

Closed via 481c018

@onobc onobc closed this as completed Sep 13, 2023
@vauvenal5
Copy link
Author

vauvenal5 commented Oct 5, 2023

Hi! So, here are a few additional inputs from our side.

We imported the timestamp-batch-task:3.0.0.
image

Composed it as two tasks one after the other:
image

Entrypoint exec works out well but entrypoint shell does not:
image

Behavior of the shell-entrypoint execution is that the CTR just blocks:
image

If you need some more information we will try to provide it.

Edit: This is run against 2.11.0

@radish172521
Copy link

Hi, I would like to know how to decide to use Schema Target? Why I am registering with springboot3, and when I run it, it still shows Schema Target= boot2
image

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

5 participants