You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/06/15 01:06:00 UTC
[jira] [Updated] (IMPALA-5605) configuration to prevent crashes
caused by thread resource limits
[ https://issues.apache.org/jira/browse/IMPALA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-5605:
----------------------------------
Target Version: Product Backlog
> configuration to prevent crashes caused by thread resource limits
> -----------------------------------------------------------------
>
> Key: IMPALA-5605
> URL: https://issues.apache.org/jira/browse/IMPALA-5605
> Project: IMPALA
> Issue Type: Documentation
> Components: Docs
> Affects Versions: Impala 2.9.0
> Reporter: Matthew Mulder
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 2.10.0
>
>
> Depending on the workload, Impala may need to create a very large number of threads. If so, it is necessary to configure the system correctly to prevent Impala from crashing because of resource limitations. Such a crash would look like this:{code}F0629 08:20:02.956413 29088 llvm-codegen.cc:111] LLVM hit fatal error: Unable to allocate section memory!
> terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread_resource_error> >'{code}To prevent this, each Impala host should be configured like this:{code}echo 2000000 > /proc/sys/kernel/threads-max
> echo 2000000 > /proc/sys/kernel/pid_max
> echo 8000000 > /proc/sys/vm/max_map_count{code}In /etc/security/limits.conf add{code}impala soft nproc 262144
> impala hard nproc 262144{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org