Error (timeout?) when loading data into Vora 1.4 -


i'm trying create vora table , append data orc file. far hit couple issues.

  1. appending data using gui (vora tools - modeler - append) seems ignore "orc" setting made in dialog. looks bug.

  2. when trying append multiple orc files total of 29mio records, following message presented:

    sap.hanavora.jdbc.voraexception: hl(9): runtime error. (could not handle api call, failure reason : execution of scheduler plan failed: internal error message: ttl exceeded, no response received: ttl=2m0s, task=1, nodes=[120];caught exception during execution of abort plan : generic runtime error.(tx_id:31)) error code 0, status error_status

it doesn't matter engine use, relational or disk, message appears anyway. there timeout setting configure?

update: details on issue #2. tx coordinator log has got following:

2017-09-18 09:54:17.088741|+1000|error|error @ processing of api call|tc103|hana v2 api|140657103492864|processrequest|v2net_request_handler.cpp(73) ... 2017-09-18 09:57:37.817268|+1000|error|execution of scheduler plan failed: internal error message: ttl exceeded, no response received: ttl=2m0s, task=1, nodes=[121];|tc103|hana v2 api|140657103492864|executephysicalplan|tc_executor.cpp(1287)^^ 2017-09-18 09:57:37.825402|+1000|error|could not found service requested type.|tc103|consul client|140657103492864|checkjson|client_impl.cpp(398)^^ 2017-09-18 09:57:37.827538|+1000|error|unable dial node 121 using cached addr xxxxx:30507 - dial tcp xxxxx:30507: getsockopt: connection refused {node=103}|v2node|v2node|42|dial|node.go(495)^^ 2017-09-18 09:58:08.084641|+1000|error|error @ processing of api call|tc103|hana v2 api|140657103492864|processrequest|v2net_request_handler.cpp(73) 

vora-manager

sep 18 09:26:30 yyyyy consul[24535]: agent: check 'service.vora-engine.yyyyy.115' missed ttl, critical sep 18 09:35:30 yyyyy consul[24535]: snapshot: found temporary snapshot: 23-915905-1504365419402.tmp sep 18 09:35:30 yyyyy consul[24535]: snapshot: found temporary snapshot: 64-915931-1504365663452.tmp sep 18 09:35:30 yyyyy consul[24535]: snapshot: found temporary snapshot: 64-915931-1504365738659.tmp sep 18 09:53:46 yyyyy consul[24535]: agent: check 'service.vora-engine.yyyyy.123' missed ttl, critical sep 18 09:55:54 yyyyy consul[24535]: memberlist: failed tcp fallback ping: read tcp yyyyy:42137->xxxxx:8301: i/o timeout sep 18 09:56:00 yyyyy consul[24535]: memberlist: failed receive: read tcp yyyyy:8301->xxxxx:50044: i/o timeout from=xxxxx:50044 sep 18 09:56:00 eba156 consul[24535]: memberlist: failed tcp fallback ping: read tcp yyyyy:42839->xxxxx:8301: i/o timeout sep 18 09:56:03 yyyyy consul[24535]: memberlist: failed tcp fallback ping: read tcp yyyyy:43179->xxxxx:8301: i/o timeout ... 

what's interesting, host xxxxx has vora computing services enabled, no control services.


Comments

Popular posts from this blog

ZeroMQ on Windows, with Qt Creator -

unity3d - Unity SceneManager.LoadScene quits application -

python - Error while using APScheduler: 'NoneType' object has no attribute 'now' -