Guillaume N. created CAMEL-20189:
------------------------------------
Summary: camel-sftp: report consumer UP after connection is
established
Key: CAMEL-20189
URL: https://issues.apache.org/jira/browse/CAMEL-20189
Project: Camel
Issue Type: Bug
Components: camel-sftp
Affects Versions: 4.0.0
Reporter: Guillaume N.
Hi,
(copied from Zulip:
https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/HealthCheck.20behavior.20for.20a.20large.20file.20SFTP.20consumer)
I'm using a SFTP component to process large files. The application uses Quarkus
and is natively built and deployed on OpenShift. And I'm using the health
checks for readiness and liveness probes.
I'm facing an edge case regarding the status:
* If there is a file on the remote SFTP when the application starts, the
status will remain DOWN until after the large file has been processed.
* If there is no file, the status is immediately UP.
Basically, the status is reporting two different states:
* If there is a file: the UP status means the first polling listed the
available files and completed an exchange (the exchange can fail)
* If there is no file: the UP status means the first polling listed the
available files (and there was none).
Consequently, there is a lot of variability in the status availability, hence
the OpenShift probe configuration must be set to the worst case to avoid
killing the pod if there's a file during startup.
Turning off the health checks for consumers is a dirty workaround.
I would like to be able to report a UP status after the first polling was able
to list the available files and before it starts an exchange.
Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
