[
https://issues.apache.org/jira/browse/NIFI-15050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-15050:
------------------------------
Fix Version/s: 2.7.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Handle 409 HTTP Conflict in KubernetesConfigMapStateProvider
> ------------------------------------------------------------
>
> Key: NIFI-15050
> URL: https://issues.apache.org/jira/browse/NIFI-15050
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I faced an occurrence where the k8s config map state provider cannot update
> the component's state because of a 409 conflict response.
> I got an error similar to:
> {code:java}
> java.io.IOException: Failed to update state for Component with ID
> [1b0d2d2a-bfeb-30de-b59f-df2326513a5f]
> - Caused by: java.io.IOException: Failed to update state for Component with
> ID [1b0d2d2a-bfeb-30de-b59f-df2326513a5f]
> - Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure
> executing: PUT at:
> https://.../nifi-component-1b0d2d2a-bfeb-30de-b59f-df2326513a5f. Message:
> Operation cannot be fulfilled on configmaps
> "nifi-component-1b0d2d2a-bfeb-30de-b59f-df2326513a5f": the object has been
> modified; please apply your changes to the latest version and try again.
> Received status: Status(apiVersion=v1, code=409,
> details=StatusDetails(causes=[], group=null, kind=configmaps,
> name=nifi-component-1b0d2d2a-bfeb-30de-b59f-df2326513a5f,
> retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status,
> message=Operation cannot be fulfilled on configmaps
> "nifi-component-1b0d2d2a-bfeb-30de-b59f-df2326513a5f": the object has been
> modified; please apply your changes to the latest version and try again,
> metadata=ListMeta(_continue=null, remainingItemCount=null,
> resourceVersion=null, selfLink=null, additionalProperties={}),
> reason=Conflict, status=Failure, additionalProperties={}). {code}
> While it is not clear how this happened, we should properly handle this HTTP
> Conflict answer by getting the latest metadata and re-applying the update.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
