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

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

GitHub user selvaganesang opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/1191

    [TRAFODION-2698] Ensure RMS can be disabled properly

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/selvaganesang/incubator-trafodion 
trafodion-2695_1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/1191.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 #1191
    
----
commit a93394647bb0506b9d2b65470f17c95ef4147569
Author: selvaganesang <selva.govindara...@esgyn.com>
Date:   2017-07-29T00:19:16Z

    [TRAFODION-2698] Ensure RMS can be disabled properly

----


> Ensure RMS can be disabled properly
> -----------------------------------
>
>                 Key: TRAFODION-2698
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2698
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: sql-exe
>    Affects Versions: any
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>             Fix For: 2.2-incubating
>
>
> By default, RMS gets started. If you stop RMS, the shared segment stay around 
> and hence all the process would continue to assume RMS is up. The proper way 
> to disable RMS is
> export SQ_START_RMS=0
> Then do sqstart
>  
> This would be the proper way to disable RMS in future.
> We encounter cores of SQL processes and improper message with the above 
> scenario. Disabling RMS in the above way ensures that the shared segment is 
> never used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to