You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Suresh Subbiah (JIRA)" <ji...@apache.org> on 2015/10/08 06:55:26 UTC
[jira] [Assigned] (TRAFODION-723) LP Bug: 1386860 - Avoid infinite
loops during startup
[ https://issues.apache.org/jira/browse/TRAFODION-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Subbiah reassigned TRAFODION-723:
----------------------------------------
Assignee: Qifan Chen
> LP Bug: 1386860 - Avoid infinite loops during startup
> -----------------------------------------------------
>
> Key: TRAFODION-723
> URL: https://issues.apache.org/jira/browse/TRAFODION-723
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-cmp
> Reporter: Roberta Marton
> Assignee: Qifan Chen
> Priority: Minor
>
> Several times in the last month, changes were made by several people that caused a compilation request during a critical operation which had a domino affect and ended up in an infinite loop.
> Examples
> During the startup protocol of the compiler process the parent sent the session user ID to the compiler process. The compiler process received the user ID and tried to do a metadata read through a CLI request to get the associated username. The metadata lookup code needs to start another arkcmp process to compiler the request. The second compiler would then start up a third compiler process to compile the metadata request. Eventually, someone would fail.
>
> In another situation, instead of starting up compiler processes, the code was starting up new embedded compiler contexts. In this case, again during start up processing, a CLI request was issued to get metadata information. This CLI request started another compiler context to compile the request, etc.
> There should be a way to detect that there is some kind of infinite loop going on and stop it before it gets out of control.
> Creating the LP bug to track this change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)