[
https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388610#comment-15388610
]
ASF GitHub Bot commented on TRAFODION-1605:
-------------------------------------------
GitHub user traflm opened a pull request:
https://github.com/apache/incubator-trafodion/pull/615
[TRAFODION-1605] sqstart hangs if ulimits not correct
add ulimit checking in sqstart
if not proper setup as Trafodion installer does, print WARNING/ERROR
This should only happen in dev environment as described in the JIRA.
Installer already handle this, so a WARNING/ERROR print should be enough.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/traflm/incubator-trafodion TRAFODION-1605-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/615.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #615
----
commit da42f9f94b13f4b6be6d46eb20e97e4352607b75
Author: Liu Ming <[email protected]>
Date: 2016-07-21T23:20:20Z
[TRAFODION-1605] sqstart hangs if ulimits not correct
----
> 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)
