[
https://issues.apache.org/jira/browse/IMPALA-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18015625#comment-18015625
]
YUBI LEE edited comment on IMPALA-13413 at 8/22/25 9:50 AM:
------------------------------------------------------------
I created a PR.
https://gerrit.cloudera.org/#/c/23333/
I tested it on private cluster at my company.
was (Author: eub):
I created a PR.
https://gerrit.cloudera.org/#/c/23333/
> num_cores flag does not work.
> -----------------------------
>
> Key: IMPALA-13413
> URL: https://issues.apache.org/jira/browse/IMPALA-13413
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.4.1
> Reporter: Yonghwan Lee
> Priority: Minor
>
> The `num_cores` Flag does not work.
>
> The cause is that CpuInfo::Init() is called before
> google::ParseCommandLineFlags(&argc, &argv, true) within the
> InitCommonRuntime function in init.cc.
>
> Other functions (e.g. DiskInfo, MemInfo, etc.) do not use the value (Gflag)
> parsed from the CommandLine in the Init() function, but in the case of
> CpuInfo, FLAGS_num_cores is used within Init().
> Since google::ParseCommandLineFlags(&argc, &argv, true) has not yet been
> called, its value is set to 0, and if (FLAGS_num_cores > 0) num_cores_ =
> FLAGS_num_cores; It is confirmed that the syntax does not work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
