-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
关于SCQL-p2p模式高可用解决方案的疑问 #420
Comments
1.SCQL目前支持任务重试,但如果OOM等原因导致服务挂掉,不会自动拉起(建议框架层做些保活、监测告警的工作) |
好的,感谢您,还有个问题就是scql run in kuscia的话,数据源路由方式是不是只能使用kuscia datamesh的方式了,是不是无法使用http路由的方式进行数据源路由?
…---原始邮件---
发件人: ***@***.***>
发送时间: 2025年1月2日(周四) 下午4:36
收件人: ***@***.***>;
抄送: "Han ***@***.******@***.***>;
主题: Re: [secretflow/scql] 关于SCQL-p2p模式高可用解决方案的疑问 (Issue #420)
1.SCQL目前支持任务重试,但如果OOM等原因导致服务挂掉,不会自动拉起(建议框架层做些保活、监测告警的工作)
2. run in kuscia有监控机制、实例保活、SCQL多实例并行、资源隔离等一些机制提升鲁棒性,但具体能否满足业务高可用的需求,建议提供相应的应用场景和kuscia同学对齐。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@jingshi-ant 麻烦您看下我最新的问题 |
数据源可以使用kuscia datemesh,也可以用embed_router_conf的形式,在engine的配置中进行配置即可。 |
可以的 |
好的,感谢 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1.想问下针对数据量大或耗时会导致服务挂掉的情况,SCQL是否有现有的高可用解决方案?
2.SCQL run in kuscia是否有对应高可用的解决方案?
The text was updated successfully, but these errors were encountered: