We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. 当前触发器调度是内存队列中维护的,则 app-server 有状态依赖,不可横向绅缩实现;只能跑单例; 主要分为定时器和事件触发器,一个触发事件应只由一个实例运行。
Describe the solution you'd like 有两种思路:
Describe alternatives you've considered 暂不考虑 引入 redis,当前未有 cache 设计; mongodb 队例,可处理定时触发器,但事件触发器是 app-server 代码层面调用的,不适宜用队列改造; 至于第3种方案,考虑伸缩环境为 kubernetes,要调研 kubernetes 绅缩策略是否支持 「标记指定实例」不释放。
大概率还是需要在应用层实现这个选举逻辑的。不能用 kubernetes 自带的伸缩能力。 那么 app-server 当前的调度器就无需 重新设计,只需要增加一个参数来控制 开关 调度器即可。 Additional context
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
当前触发器调度是内存队列中维护的,则 app-server 有状态依赖,不可横向绅缩实现;只能跑单例;
主要分为定时器和事件触发器,一个触发事件应只由一个实例运行。
Describe the solution you'd like
有两种思路:
Describe alternatives you've considered
暂不考虑 引入 redis,当前未有 cache 设计;
mongodb 队例,可处理定时触发器,但事件触发器是 app-server 代码层面调用的,不适宜用队列改造;
至于第3种方案,考虑伸缩环境为 kubernetes,要调研 kubernetes 绅缩策略是否支持 「标记指定实例」不释放。
大概率还是需要在应用层实现这个选举逻辑的。不能用 kubernetes 自带的伸缩能力。
那么 app-server 当前的调度器就无需 重新设计,只需要增加一个参数来控制 开关 调度器即可。
Additional context
The text was updated successfully, but these errors were encountered: