[
https://issues.apache.org/jira/browse/TRAFODION-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289253#comment-15289253
]
ASF GitHub Bot commented on TRAFODION-1956:
-------------------------------------------
Github user DaveBirdsall commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/488#discussion_r63736792
--- Diff: core/sql/cli/SessionDefaults.cpp ---
@@ -193,6 +194,8 @@ SessionDefaults::SessionDefaults(CollHeap * heap)
setEspStopIdleTimeout(60);
// Default is 1800 (idle ESPs time out in 30 minutes)
setEspIdleTimeout(30*60);
+ // Default is 1800 (Compiler Idle time out in 30 minutes)
+ setCompilerIdleTimeout(30*60);
--- End diff --
What do we use the compiler for now? SQL compiles are all done in the
embedded compiler. I'm guessing DDL and some utilities are the only reasons we
use a separate compiler. Since these operations are relatively infrequent, I
wonder if we should make the timeout shorter (say, 5 minutes) since the
compiler will be idle most the time. It would reduce the process and memory
footprint on the system.
> timeout in tdm_arkcmp process
> -----------------------------
>
> Key: TRAFODION-1956
> URL: https://issues.apache.org/jira/browse/TRAFODION-1956
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-cmp
> Affects Versions: any
> Reporter: Henry Lin
> Assignee: Selvaganesan Govindarajan
> Labels: patch
>
> The tdm_arkcmp is spawned for extra sql compilation as needed, but the
> tdm_arkcmp process will never stop and become an orphan process. It would be
> better to introduce a mechanism to let tdm_arkcmp stop, e.g. timeout for an
> idle tdm_arkcmp.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
