[
https://issues.apache.org/jira/browse/DRILL-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261224#comment-16261224
]
ASF GitHub Bot commented on DRILL-4286:
---------------------------------------
Github user paul-rogers commented on a diff in the pull request:
https://github.com/apache/drill/pull/921#discussion_r152361270
--- Diff:
protocol/src/main/java/org/apache/drill/exec/proto/beans/RpcType.java ---
@@ -25,28 +25,8 @@
HANDSHAKE(0),
ACK(1),
GOODBYE(2),
- RUN_QUERY(3),
- CANCEL_QUERY(4),
- REQUEST_RESULTS(5),
- RESUME_PAUSED_QUERY(11),
- GET_QUERY_PLAN_FRAGMENTS(12),
- GET_CATALOGS(14),
- GET_SCHEMAS(15),
- GET_TABLES(16),
- GET_COLUMNS(17),
- CREATE_PREPARED_STATEMENT(22),
- GET_SERVER_META(8),
- QUERY_DATA(6),
- QUERY_HANDLE(7),
- QUERY_PLAN_FRAGMENTS(13),
- CATALOGS(18),
- SCHEMAS(19),
- TABLES(20),
- COLUMNS(21),
- PREPARED_STATEMENT(23),
- SERVER_META(9),
- QUERY_RESULT(10),
- SASL_MESSAGE(24);
+ REQ_RECORD_BATCH(3),
+ SASL_MESSAGE(4);
--- End diff --
The change seems to be that messages are dropped. That can't be good. The
only diff that should show up here is the addition of your new state codes.
The other explanation is that master is wrong, which would be a bad state
of affairs.
> 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)
