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

ASF GitHub Bot commented on DRILL-4286:
---------------------------------------

Github user arina-ielchiieva commented on the issue:

    https://github.com/apache/drill/pull/921
  
    @paul-rogers is right, there is something wrong with the protos @dvjyothsna 
has generated.
    I took master branch and generated protos. No changes so these extra 
changes we see are wrong. Also I have created branch where I have added changes 
in protos from this PR [1] and from the diff it can be seen that no extra 
changes as well [2].
    
    @dvjyothsna please address this issue.
    If it helps:
    I have installed protoc:
    ```
    protoc --version
    libprotoc 2.5.0
    ```
    and generated using the following:
    ```
    cd ~/git_repo/drill/protocol
    mvn process-sources -P proto-compile
    ```
    [1] https://github.com/arina-ielchiieva/drill/tree/DRILL-4386-proto
    [2] 
https://github.com/arina-ielchiieva/drill/commit/07af545ab27b77e5f86002d4ce0f54b3dd371343


> Have an ability to put server in quiescent mode of operation
> ------------------------------------------------------------
>
>                 Key: DRILL-4286
>                 URL: https://issues.apache.org/jira/browse/DRILL-4286
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Execution - Flow
>            Reporter: Victoria Markman
>            Assignee: Venkata Jyothsna Donapati
>
> I think drill will benefit from mode of operation that is called "quiescent" 
> in some databases. 
> From IBM Informix server documentation:
> {code}
> Change gracefully from online to quiescent mode
> Take the database server gracefully from online mode to quiescent mode to 
> restrict access to the database server without interrupting current 
> processing. After you perform this task, the database server sets a flag that 
> prevents new sessions from gaining access to the database server. The current 
> sessions are allowed to finish processing. After you initiate the mode 
> change, it cannot be canceled. During the mode change from online to 
> quiescent, the database server is considered to be in Shutdown mode.
> {code}
> This is different from shutdown, when processes are terminated. 



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

Reply via email to