[ 
https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389989#comment-15389989
 ] 

ASF GitHub Bot commented on TRAFODION-1605:
-------------------------------------------

Github user DaveBirdsall commented on a diff in the pull request:

    https://github.com/apache/incubator-trafodion/pull/615#discussion_r71923574
  
    --- Diff: core/sqf/sql/scripts/sqstart ---
    @@ -245,6 +245,39 @@ function checkKerberos {
        return 0
     }
     
    +function checkUlimit {
    +  
    + #check max_pid 
    + userProc=`cat /proc/sys/kernel/pid_max`
    + if [[ $userProc -gt 65535 ]] ; then
    +    echoLog ""
    +    echoLog "ERROR: detect issue during startup, please make sure your 
kernel parameter (sysctl) setup correctly"
    --- End diff --
    
    Suggested wordsmith: "Error: issue detected during startup. Please make 
sure your kernel parameter (sysctl) is set up correctly."


> sqstart hangs if ulimits not correct
> ------------------------------------
>
>                 Key: TRAFODION-1605
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1605
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: Build Infrastructure
>            Reporter: Roberta Marton
>            Assignee: liu ming
>
> If someone downloads a source tar file or uses the Trafodion git repository, 
> after building they need to install the results on their system.  If the 
> ulimits on the system are not sufficient, then sqlci start hangs.  The 
> customer has to kill sqlci and then kill all the processes in flight.
> This happens when you perform the build instructions and choose the 
> "install_local_hadoop" option.  The Trafodion Installer should already be 
> checking for this situation.
> Perhaps add a check before sqlci starts to make sure the correct limits are 
> set.
> Recommended limits:
> ulimit –a
>  core file size                    (blocks, -c) 1000000
> data seg size                    (kbytes, -d) unlimited
> scheduling priority            (-e) 0
> file size                             (blocks, -f) unlimited
> pending signals                (-i) 515196
> max locked memory         (kbytes, -l) 49595556
> max memory size             (kbytes, -m) unlimited
> open files                          (-n) 32000
> pipe size                           (512 bytes, -p) 8
> POSIX message queues  (bytes, -q) 819200
> real-time priority               (-r) 0
> stack size                         (kbytes, -s) 10240
> cpu time                           (seconds, -t) unlimited
> max user processes         (-u) 267263
> virtual memory                 (kbytes, -v) unlimited
> file locks                           (-x) unlimited



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to