You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "MonsterChenzhuo (via GitHub)" <gi...@apache.org> on 2023/04/08 14:40:07 UTC
[GitHub] [incubator-seatunnel] MonsterChenzhuo opened a new pull request, #4523: [WIP][Feature][Zeta] Support on k8s mode deployment
MonsterChenzhuo opened a new pull request, #4523:
URL: https://github.com/apache/incubator-seatunnel/pull/4523
<!--
Thank you for contributing to SeaTunnel! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
## Contribution Checklist
- Make sure that the pull request corresponds to a [GITHUB issue](https://github.com/apache/incubator-seatunnel/issues).
- Name the pull request in the form "[Feature] [component] Title of the pull request", where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
- Minor fixes should be named following this pattern: `[hotfix] [docs] Fix typo in README.md doc`.
-->
## Purpose of this pull request
close #4386
<!-- Describe the purpose of this pull request. For example: This pull request adds checkstyle plugin.-->
## Check list
* [ ] Code changed are covered with tests, or it does not need tests for reason:
* [ ] If any new Jar binary package adding in your PR, please add License Notice according
[New License Guide](https://github.com/apache/incubator-seatunnel/blob/dev/docs/en/contribution/new-license.md)
* [ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
* [ ] If you are contributing the connector code, please check that the following files are updated:
1. Update change log that in connector document. For more details you can refer to [connector-v2](https://github.com/apache/incubator-seatunnel/tree/dev/docs/en/connector-v2)
2. Update [plugin-mapping.properties](https://github.com/apache/incubator-seatunnel/blob/dev/plugin-mapping.properties) and add new connector information in it
3. Update the pom file of [seatunnel-dist](https://github.com/apache/incubator-seatunnel/blob/dev/seatunnel-dist/pom.xml)
* [ ] Update the [`release-note`](https://github.com/apache/incubator-seatunnel/blob/dev/release-note.md).
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-seatunnel] hailin0 commented on pull request #4523: [WIP][Feature][Zeta] Support on k8s mode deployment
Posted by "hailin0 (via GitHub)" <gi...@apache.org>.
hailin0 commented on PR #4523:
URL: https://github.com/apache/incubator-seatunnel/pull/4523#issuecomment-1502051351
> SeaTunnel engine uses hazelcast as discovery framework and hazelcast has Kubernetes discovery plugin, why do we want to replicate the function here?
+1
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-seatunnel] MonsterChenzhuo commented on pull request #4523: [WIP][Feature][Zeta] Support on k8s mode deployment
Posted by "MonsterChenzhuo (via GitHub)" <gi...@apache.org>.
MonsterChenzhuo commented on PR #4523:
URL: https://github.com/apache/incubator-seatunnel/pull/4523#issuecomment-1553019882
@hailin0 @kezhenxu94
Hazelcast indeed supports K8s deployment, but the K8s deployment I need to implement is not simply about deploying several persistent Hazelcast clusters and submitting through the client.
What I need is a deployment method similar to Flink's K8s Application Mode to support the deployment of over 4000 batch tasks per day.
In Application Mode, user code is bundled with the SeaTunnel engine image, as it runs the main() method of the user code on the cluster. Application Mode ensures that all SeaTunnel engine components are properly cleaned up after the application terminates.
By using the Application Mode:
For production use, this mode provides better isolation for applications.
It is able to dynamically allocate and deallocate TaskManagers according to the required resources, as it can communicate directly with Kubernetes.
It greatly simplifies the deployment, configuration, and lifecycle management of SeaTunnel engine resources on Kubernetes.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [seatunnel] MonsterChenzhuo closed pull request #4523: [WIP][Feature][Zeta] Support on k8s Application Mode deployment
Posted by "MonsterChenzhuo (via GitHub)" <gi...@apache.org>.
MonsterChenzhuo closed pull request #4523: [WIP][Feature][Zeta] Support on k8s Application Mode deployment
URL: https://github.com/apache/seatunnel/pull/4523
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org