broker OOMKilled

[carloscao0928]

先贴下我的配置：

nameservice 可以启动，但broker不行，查看logs的话

describe的话，结果如下：

不知道怎么处理，谢谢

[liuruiyiyang]

It seems that the broker is OOMKilled. Could you please try to use the default configuration of broker CR:

resources:
    requests:
      memory: "2048Mi"
      cpu: "250m"
    limits:
      memory: "4096Mi"
      cpu: "500m"

and see if it works.

Thanks for your feedback!

[carloscao0928]

看来经纪人是OOMKilled。您能否尝试使用代理CR的默认配置：

resources:
    requests:
      memory: "2048Mi"
      cpu: "250m"
    limits:
      memory: "4096Mi"
      cpu: "500m"

看看是否可行。

感谢您的反馈意见！

我就是先用默认的报错 才加大内存和cpu，发现还是报错，所以提交下问题

[liuruiyiyang]

Does your environment has the requested resource of memory? Maybe you should try smaller resource like

resources:
    requests:
      memory: "1024Mi"
      cpu: "250m"
    limits:
      memory: "2048Mi"
      cpu: "500m"

[liuruiyiyang]

看来经纪人是OOMKilled。您能否尝试使用代理CR的默认配置：

resources:
    requests:
      memory: "2048Mi"
      cpu: "250m"
    limits:
      memory: "4096Mi"
      cpu: "500m"

看看是否可行。
感谢您的反馈意见！

我就是先用默认的报错 才加大内存和cpu，发现还是报错，所以提交下问题

Is the default config also OOMKilled ?

[carloscao0928]

看来经纪人是OOMKilled。您能否尝试使用代理CR的默认配置：

resources:
    requests:
      memory: "2048Mi"
      cpu: "250m"
    limits:
      memory: "4096Mi"
      cpu: "500m"

看看是否可行。
感谢您的反馈意见！

我就是先用默认的报错 才加大内存和cpu，发现还是报错，所以提交下问题

Is the default config also OOMKilled ?

不起作用

[liuruiyiyang]

@carloscao0928 你试了把request 和limits 内存再调小一点吗？ 如果还不行是否是你的服务器内存不够或者docker对容器内存有什么限制？

Have you tried configure smaller memory resource? If still not work please check if your host has enough memory or your docker has some restrains on container memory resource.

[carloscao0928]

@carloscao0928 你试了把request 和limits 内存再调小一点吗？ 如果还不行是否是你的服务器内存不够或者docker对容器内存有什么限制？

Have you tried configure smaller memory resource? If still not work please check if your host has enough memory or your docker has some restrains on container memory resource.

试过了没有用，服务器够的，12cpu 48gram，容器也没有限制

[liuruiyiyang]

Currently the broker startup script use max(min(1/2 ram, 1024MB), min(1/4 ram, 8GB)) to calculate JVM max heap size.
Try to set request memory more than 8GB? like:

resources:
    requests:
      memory: "10240Mi"
      cpu: "250m"
    limits:
      memory: "14240Mi"
      cpu: "500m"

[carloscao0928]

Currently the broker startup script use max(min(1/2 ram, 1024MB), min(1/4 ram, 8GB)) to calculate JVM max heap size.
Try to set request memory more than 8GB? like:

resources:
    requests:
      memory: "10240Mi"
      cpu: "250m"
    limits:
      memory: "14240Mi"
      cpu: "500m"

its works.

[drivebyer]

the broker startup script allocated JVM size based on host memory. When deploy on k8s, i think the JVM size should be calculated by container view.