Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

When a replication job is rejected , the error message about the reason is not shown.

Description

steps to reproduce:

  1. create an 6.6 instance in autopush

  2. connect to GKE in Tenant Project

  3. modify the CR to set app.max.concurrent.launching to 1

  4. restart the appfabric pod

  5. deploy a batch pipeline and a replication job

  6. run the batch pipeline and then run the replication job

  7. the replication job launch will be rejected due to current launch threshold, but error message is now shown.

 

If we run the replication job first and then the batch pipeline, the batch pipeline will be rejected with error message shown on top banner.

Release Notes

None

Activity

Show:

Sean PodestaFebruary 10, 2022 at 8:07 PM

this will be fixed by

Sean PodestaFebruary 10, 2022 at 7:29 PM

Sean ZhouFebruary 10, 2022 at 6:45 PM

shared the CDF instance I have with Sean for reproducing the problem

Sean ZhouFebruary 10, 2022 at 4:32 PM

yes, this is new in 6.6. modify CR means edit the Custom Resource of GKE : kubectl edit cdapmaster.cdap.cdap.io/$INSTANCE_NAME

Sean PodestaFebruary 10, 2022 at 5:18 AM

is this new behavior? what does modify the cr mean?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Affects versions

Fix versions

Priority

Created February 10, 2022 at 4:52 AM
Updated February 11, 2022 at 2:20 AM
Resolved February 11, 2022 at 2:20 AM