You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by "fuweng11 (via GitHub)" <gi...@apache.org> on 2024/01/09 03:26:40 UTC
[I] [Bug][Manager] Sink remains in configuration after standalone cluster allocation failure [inlong]
fuweng11 opened a new issue, #9552:
URL: https://github.com/apache/inlong/issues/9552
### What happened
Sink remains in configuration after standalone cluster allocation failure.
### What you expected to happen
Sink changes to configuration failure after standalone cluster allocation failure
### How to reproduce
Configure ES sink and do not allocate standalone clusters.
### Environment
_No response_
### InLong version
master
### InLong Component
InLong Manager
### Are you willing to submit PR?
- [X] Yes, I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Manager] Sink remains in configuration after standalone cluster allocation failure [inlong]
Posted by "dockerzhang (via GitHub)" <gi...@apache.org>.
dockerzhang closed issue #9552: [Bug][Manager] Sink remains in configuration after standalone cluster allocation failure
URL: https://github.com/apache/inlong/issues/9552
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org