Calcite server, the error was: 'THRIFT_EAGAIN (timed out)',

Follow

Sumit

• February 12, 2020 07:52

2020-02-12T11:40:06.221621 I 55710 Calcite.cpp:475 User calcite catalog WICP_MAPD_DB sql 'select count(1) from CDR_EVR WHERE IDENTITY_ID=’sumit';'

2020-02-12T11:40:11.221872 F 55710 Calcite.cpp:509 Error occurred trying to communicate with Calcite server, the error was: 'THRIFT_EAGAIN (timed out)', omnisci_server restart will be required

2020-02-12T11:40:11.517439 I 55710 MapDServer.cpp:1038 Interrupt signal (6) received.

[root@ ~]# date

Wed Feb 12 11:41:31 +04 2020

[root@ ~]# systemctl status omnisci_server

● omnisci_server.service - OmniSci database server

Loaded: loaded (/usr/lib/systemd/system/omnisci_server.service; enabled; vendor preset: disabled)

Active: active (running) since Wed 2020-02-12 11:40:24 +04; 1min 10s ago

Main PID: 73868 (omnisci_server)

Tasks: 108

CGroup: /system.slice/omnisci_server.service

       ├─73868 /opt/omnisci//bin/omnisci_server --config /opt/data/omnisci.conf

       └─73871 -Xmx1024m -DMAPD_LOG_DIR=/opt/data/data -jar /opt/omnisci/bin/calcite-1.0-SNAPSHOT-jar-with-dependencies.jar -e /opt/omnisci/QueryEngine/ -d /opt/data/data...

Feb 12 11:40:24 wicputility1 systemd[1]: Started OmniSci database server.

Feb 12 11:40:24 wicputility1 omnisci_server[73868]: 2020-02-12T11:40:24.464557 E 73868 MapDHandler.cpp:225 This build isn't CUDA enabled, will run on CPU

1

• 

  Sumit

  • February 12, 2020 07:53

  after updating the server, whenever i am running this query, system is crashing and need to restart the OMNISCI server module.

  0

  Comment actions Permalink
• 

  Candido Dessanti

  • February 12, 2020 14:09

  Hi @Sumit,

  what about running a count(*) or a count(IDENTITY_ID)?

  is identity_id a dictionary encoded or a plain text?

  0

  Comment actions Permalink
• 

  Sumit

  • February 13, 2020 12:38

  it is text

  IDENTITY_ID TEXT ENCODING DICT(32)

  0

  Comment actions Permalink
• 

  Candido Dessanti

  • February 14, 2020 13:24

  Hi,

  I don't think the problem relies in which query you run against the table.

  Anyway i replied on the other thread you opened about this error

  0

  Comment actions Permalink

Please sign in to leave a comment.