Skip to content

[BUG] Flag "temp_file_limit" not recognized #156

@cberge908

Description

@cberge908

Hi,

we're using chart version 2.17.1 and want to set the temp_file_limit flag to -1.
Setting this flag to any kind of value ends up in an error:

DNS addr resolve: yb-tserver-0.yb-tservers.yugabyte.svc.cluster.local
DNS addr resolve success.
Bind ipv4: 10.244.2.47 port 9100
Bind success.
DNS addr resolve: yb-tserver-0.yb-tservers.yugabyte.svc.cluster.local
DNS addr resolve success.
Bind ipv4: 10.244.2.47 port 9100
Bind success.
DNS addr resolve: 0.0.0.0
DNS addr resolve success.
Bind ipv4: 0.0.0.0 port 9000
Bind success.
DNS addr resolve: yb-tserver-0.yb-tservers.yugabyte.svc.cluster.local
DNS addr resolve success.
Bind ipv4: 10.244.2.47 port 9042
Bind success.
DNS addr resolve: 0.0.0.0
DNS addr resolve success.
Bind ipv4: 0.0.0.0 port 5433
Bind success.
2023-02-21 10:41:41,857 [INFO] k8s_parent.py: Core files will be copied to '/mnt/disk0/cores'
2023-02-21 10:41:41,857 [INFO] k8s_parent.py: core_pattern is: core
ERROR: unknown command line flag 'temp_file_limit'
2023-02-21 10:41:41,872 [INFO] k8s_parent.py: core_pattern is: core
2023-02-21 10:41:41,872 [INFO] k8s_parent.py: Skipping copy of core files: '/mnt/disk0/cores' and '/mnt/disk0/cores' are the same directories
2023-02-21 10:41:41,872 [INFO] k8s_parent.py: Copied 0 core files to '/mnt/disk0/cores'
Stream closed EOF for yugabyte/yb-tserver-0 (yb-tserver)

This seems to be a bug, setting other flags seem to work fine.

Cheers,
cberge908

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions