impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Mulder (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IMPALA-5605) configuration to prevent crashes caused by thread resource limits
Date Thu, 29 Jun 2017 23:59:00 GMT
Matthew Mulder created IMPALA-5605:
--------------------------------------

             Summary: 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: John Russell
             Fix For: Impala 2.9.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
(v6.4.14#64029)

Mime
View raw message