Uploaded image for project: 'Apache Drill'
  1. Apache Drill
  2. DRILL-1327

Any subsequent query may hung in sqlline after you cancel one query in the same session

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 0.4.0
    • Fix Version/s: 0.6.0
    • Labels:
      None
    • Environment:

      MapR 3.1.1
      Drill 0.4.0

      Description

      This is another issue related to DRILL-1326.
      If we cancel a query in sqlline, subsequent query may hung.
      I can reproduce it almost every time.

      How to reproduce:
      1. Logon sqlline, run below SQL:

      select *
       from cp.`employee.json` a, cp.`employee.json` b
       where a.position_id=b.position_id ;
      

      2. When it is printing the results for about 3 seconds, type "ctrl-c" to stop it.
      3. Then any subsequent query will hung.

      ===============================

      For example,

      | 110         | Josie Underwood | Josie      | Underwood  | 15          | Store Permanent Checker | 7          | 15            | 1914-02-02 | 1996-01-01 00:00:00.0 | 8200.0     | 101       |
      | 110         | Josie Underwood | Josie      | Underwood  | 15          | Store Permanent Checker | 7          | 15            | 1914-02-02 | 1996-01-01 00:00:00.0 | 8200.0     | 101       |
      | 110         | Josie Underwood | Josie      | Underwood  | 15          | Store Permanent Checker | 7          | 15            | 1914-02-02 | 1996-01-01 00:00:00.0 | 8200.0     | 101       |
      | 110         | Josie Underwood | Josie      | Underwood  | 15          | Store Permanent Checker | 7          | 15            | 1914-02-02 | 1996-01-01 00:00:00.0 | 8200.0     | 101       |
      +-------------+------------+------------+------------+-------------+----------------+------------+---------------+------------+------------+------------+---------------+-----------------+--+
      11,744 rows selected (2.879 seconds)
      0: jdbc:drill:zk=node1.xxx.com:5181,node3.>
      Command canceled.
      0: jdbc:drill:zk=node1.xxx.com:5181,node3.>
      Command canceled.
      0: jdbc:drill:zk=node1.xxx.com:5181,node3.>
      0: jdbc:drill:zk=node1.xxx.com:5181,node3.> SELECT TABLE_SCHEMA, TABLE_NAME, TABLE_TYPE
      . . . . . . . . . . . . . . . . . . . . . . .> FROM INFORMATION_SCHEMA.`TABLES`
      . . . . . . . . . . . . . . . . . . . . . . .> ORDER BY TABLE_NAME DESC;
      
      

      In the end, we have "ctrl-z" and "kill -9 %1" to exit the sqlline.
      After that, the SQL become "Running Queries" forever.
      We need to fix this because it looks like the sqlline is not stable.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              haozhu Hao Zhu

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment