vertica - VSql client hangs after restore -
after restoring database backup using vbr utility, when start database, queries fail execute. vertica log shows query not executed. moreover, cannot exit vsql or cancel command , cluster no longer accepts queries. not sure went wrong since restore completed successfully. ideas how can fixed ?
log entries:
2017-09-11 08:50:24.681 init session:0x7ff780011dc0 [session] [query] tx:0(******.-1964:0x19cc2) select 1; 2017-09-11 08:53:25.001 tm mergeout(01):0x7ff77807c620-a0000000000e02 [txn] begin txn: a0000000000e02 'mergeout: tuple mover' 2017-09-11 08:53:27.257 tm mergeout(01):0x7ff77807c620-a0000000000e02 [tm] tuple mover: nothing merge out 2017-09-11 08:53:27.439 tm mergeout(01):0x7ff77807c620-a0000000000e02 [tm] tuple mover: no dv merge out 2017-09-11 08:53:27.439 tm mergeout(01):0x7ff77807c620-a0000000000e02 [txn] rollback txn: a0000000000e02 'mergeout: tuple mover' 2017-09-11 08:53:27.517 tm mergeout(01):0x7ff77807c620 [util] task 'tm mergeout(01)' enabled 2017-09-11 08:53:50.001 tm mergeout(00):0x7ff77807c620-a0000000000e03 [txn] begin txn: a0000000000e03 'mergeout: tuple mover' 2017-09-11 08:53:52.056 tm mergeout(00):0x7ff77807c620-a0000000000e03 [tm] tuple mover: nothing merge out 2017-09-11 08:53:52.219 tm mergeout(00):0x7ff77807c620-a0000000000e03 [tm] tuple mover: no dv merge out 2017-09-11 08:53:52.219 tm mergeout(00):0x7ff77807c620-a0000000000e03 [txn] rollback txn: a0000000000e03 'mergeout: tuple mover' 2017-09-11 08:53:52.286 tm mergeout(00):0x7ff77807c620-a0000000000e04 [txn] begin txn: a0000000000e04 'collectmovestoragejobs' 2017-09-11 08:53:52.467 tm mergeout(00):0x7ff77807c620-a0000000000e04 [txn] rollback txn: a0000000000e04 'collectmovestoragejobs' 2017-09-11 08:53:52.472 tm mergeout(00):0x7ff77807c620 [util] task 'tm mergeout(00)' enabled 2017-09-11 08:54:11.008 tm moveout:0x7ff77807c620-a0000000000e05 [txn] begin txn: a0000000000e05 'moveout: tuple mover' 2017-09-11 08:54:11.008 tm moveout:0x7ff77807c620-a0000000000e05 [txn] rollback txn: a0000000000e05 'moveout: tuple mover' 2017-09-11 08:54:11.009 tm moveout:0x7ff77807c620 [util] task 'tm moveout' enabled 2017-09-11 08:54:11.013 lgelaggingcheck:0x7ff778012ae0-a0000000000e06 [txn] begin txn: a0000000000e06 'recovery: last epoch' 2017-09-11 08:54:11.104 lgelaggingcheck:0x7ff778012ae0-a0000000000e06 [txn] starting commit: txn: a0000000000e06 'recovery: last epoch' 2017-09-11 08:54:11.106 lgelaggingcheck:0x7ff778012ae0 [txn] commit complete: txn: a0000000000e06 @ epoch 0x245ec 2017-09-11 08:54:11.106 lgelaggingcheck:0x7ff778012ae0-a0000000000e07 [txn] begin txn: a0000000000e07 'check lge' 2017-09-11 08:54:11.106 lgelaggingcheck:0x7ff778012ae0-a0000000000e07 [txn] rollback txn: a0000000000e07 'check lge' 2017-09-11 08:54:11.107 lgelaggingcheck:0x7ff778012ae0 [util] task 'lgelaggingcheck' enabled 2017-09-11 08:55:37.352 init session:0x7ff780011720 @v_mn_node0001: 00000/2705: connection received: host=********* port=**** (conncnt 6) 2017-09-11 08:55:37.352 init session:0x7ff780011720 @v_mn_node0001: 00000/4540: received ssl negotiation startup packet 2017-09-11 08:55:37.352 init session:0x7ff780011720 @v_mn_node0001: 00000/4691: sending ssl negotiation response 'n' 2017-09-11 08:55:37.353 init session:0x7ff780011720 @v_mn_node0001: 00000/4686: authentication - sendauthrequest: user=**** database=**** host=******** authtype=3 2017-09-11 08:55:37.353 init session:0x7ff780011720-a0000000000e08 [txn] begin txn: a0000000000e08 'check_login_history' 2017-09-11 08:55:37.353 init session:0x7ff780011720-a0000000000e08 [txn] rollback txn: a0000000000e08 'check_login_history'
any appreciated. !
Comments
Post a Comment