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

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

Github user arina-ielchiieva commented on the issue:

    https://github.com/apache/drill/pull/921
  
    @dvjyothsna all tests has passed. Though there is significant performance 
degradation.
    Before your changes unit test run takes ~ 33 minutes, after ~ 1 hour 18 
minutes. 
    For example, exec package:
    before `[INFO] exec/Java Execution Engine ......................... SUCCESS 
[17:14 min]`,
    after `[INFO] exec/Java Execution Engine ......................... SUCCESS 
[56:45 min]`.
    Since you did not add that many unit tests, could you please explain the 
reason of such performance degradation and ideally fix it.
    Attached two unit tests outputs in Jira.



> 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
>    Affects Versions: 1.11.0
>            Reporter: Victoria Markman
>            Assignee: Venkata Jyothsna Donapati
>              Labels: doc-impacting, ready-to-commit
>             Fix For: 1.12.0
>
>         Attachments: consoleText.txt
>
>
> 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