[Discuss][Zeta] Support pekko as new distributed service framework

[hailin0]

Search before asking

• [X] I had searched in the feature and found no similar feature requirement.

Description

Currently we use hazelcast as the distributed service framework, but we found some problems：

• Monitor tools are subject to licensing restrictions
• Future concerns about licensing https://github.com/apache/seatunnel/issues/7513
• The community is not open enough

pekko

• https://pekko.apache.org/

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[hailin0]

Do you have any suggestions? @Hisoka-X

[Hisoka-X]

+1 for pekko. cc @apache/seatunnel-committers

[liugddx]

+1. Sounds good.

[liugddx]

This is another option https://github.com/ray-project/ray

[dailai]

+1

[zhangshenghang]

+1

[caicancai]

+1, Based on my understanding of pekko, this is a very large project

[Xuxiaotuan]

+1

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

[dybyte]

It seems the first step is to decouple SeaTunnel from Hazelcast by extracting a small interface layer. cc @zhangshenghang @davidzollo

[zhangshenghang]

It seems the first step is to decouple SeaTunnel from Hazelcast by extracting a small interface layer. cc @zhangshenghang @davidzollo

Yes, this function is a relatively major change. It needs to have a thorough plan demonstration before starting. @dybyte