Tags: dapr/dapr
Tags
[1.16] Propagation of traceparent in grpc pubsub (#9237) * chore: Add traceparent to grpc output metadata Signed-off-by: Javier Aliaga <[email protected]> * chore: Update component contrib 1.16.5 Signed-off-by: Javier Aliaga <[email protected]> --------- Signed-off-by: Javier Aliaga <[email protected]>
[1.16] Deleted Jobs in all prefix matching deleted Namespaces (#9232) * Deleted Jobs in all prefix matching deleted Namespaces Problem Deleting a namespace in Kubernetes will delete all the associated jobs in that namespace. If there are any other namespaces with a name which has a prefix matching the deleted namespace, the jobs in those namespaces will also be deleted (i.e. deleting namespace "test" will also delete jobs in namespace "test-1" or "test-abc"). Impact Deleting a namespace will delete jobs in other namespaces with prefix matching the deleted namespace. Root Cause Prefix logic did not terminate the prefix match with an exact match so that deleting a namespace would delete jobs in other namespaces with prefix matching the deleted namespace. Solution The prefix logic has been updated to ensure that only jobs in the exact deleted namespace are deleted. Signed-off-by: joshvanl <[email protected]> * Lint Signed-off-by: joshvanl <[email protected]> * Fix unit tests Signed-off-by: joshvanl <[email protected]> * Point go-etcd-cron to joshvanl fork diagridio/go-etcd-cron#104 Signed-off-by: joshvanl <[email protected]> * Update github.com/diagridio/go-etcd-cron to v0.9.2 Signed-off-by: joshvanl <[email protected]> --------- Signed-off-by: joshvanl <[email protected]>
chore: Update component-contrib dep (#9204) Signed-off-by: Javier Aliaga <[email protected]> Co-authored-by: Cassie Coyle <[email protected]>
[1.16] Prevent infinite loop when workflow state is corrupted or dest… …royed (#9158) * Prevent infinite loop when workflow state is corrupted or destroyed Problem Dapr workflows could enter an infinite reminder loop when the workflow state in the actor state store is corrupted or destroyed. Impact Dapr workflows would enter an infinite loop of reminder calls. Root Cause When a workflow reminder is triggered, the workflow state is loaded from the actor state store. If the state is corrupted or destroyed, the workflow would not be able to progress and would keep re-triggering the same reminder indefinitely. Solution Do not retry the reminder if the workflow state cannot be loaded, and instead log an error and exit the workflow execution. Signed-off-by: joshvanl <[email protected]> * lint Signed-off-by: joshvanl <[email protected]> * Add eventually for metrics Signed-off-by: joshvanl <[email protected]> --------- Signed-off-by: joshvanl <[email protected]>
Blocked Placement dissemination with high Scheduler dataset (#9129) Problem Disseminations would hang for long periods of time when the Scheduler dataset was large. Impact Dissemination could take up to hours to complete, causing reminders to not be delivered for a long period of time. Root Cause The reminder migration of state store to scheduler reminders does a full decoded scan of the Scheduler database, which would take a long time if there were many entries. During this time the dissemination would be blocked. Solution Limit the maximum time spent doing the migration to 3 seconds. Expose a new `global.reminders.skipMigration="true"` helm chart value which will skip the migration entirely. Signed-off-by: joshvanl <[email protected]>
add more debug logs to placement (#9103) * add more debug logs to placement Signed-off-by: Fabian Martinez <[email protected]> * update release notes Signed-off-by: Fabian Martinez <[email protected]> * update table Signed-off-by: Fabian Martinez <[email protected]> --------- Signed-off-by: Fabian Martinez <[email protected]> Signed-off-by: Josh van Leeuwen <[email protected]> Co-authored-by: Josh van Leeuwen <[email protected]>
feat: update release notes (#9102) Signed-off-by: nelson.parente <[email protected]>
PreviousNext