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
Please answer some questions before submitting your issue. Thanks!
2.3.0
在K8S集群中,当采用“第一个”等固定路由策略时,可以保证同一个任务一定被调度到同一个实例
K8S集群中,运行Executor的pod一旦发生扩所容或者重启,“第一个”等固定路由策略就不能保证同一个任务被调度到同一个实例
在K8S集群中运行XXL-JOB,然后发生pod变化
我在k8s集群部署了XXL-JOB,pod重启以及扩缩容会导致address_list发生变化,导致“第一个”“一致性Hash”这类策略不能保证任务打到同一个实例上,进而导致“丢弃后续调度”策略失效。请问这个有办法解决吗
The text was updated successfully, but these errors were encountered:
路由规则可以改成 第一个 默认找第一个执行器执行
Sorry, something went wrong.
No branches or pull requests
Please answer some questions before submitting your issue. Thanks!
Which version of XXL-JOB do you using?
2.3.0
Expected behavior
在K8S集群中,当采用“第一个”等固定路由策略时,可以保证同一个任务一定被调度到同一个实例
Actual behavior
K8S集群中,运行Executor的pod一旦发生扩所容或者重启,“第一个”等固定路由策略就不能保证同一个任务被调度到同一个实例
Steps to reproduce the behavior
在K8S集群中运行XXL-JOB,然后发生pod变化
Other information
我在k8s集群部署了XXL-JOB,pod重启以及扩缩容会导致address_list发生变化,导致“第一个”“一致性Hash”这类策略不能保证任务打到同一个实例上,进而导致“丢弃后续调度”策略失效。请问这个有办法解决吗
The text was updated successfully, but these errors were encountered: