Can someone suggest potential solutions to this problem? It seems as if the moveout process on the table doesn't complete, but becomes a zombie process, causing any INSERT/UPDATEs on the table to fail. The error message is below:
('55V03', '[55V03] ERROR: Unavailable: initiator locks for query - Locking failure:
Timed out X locking Table:myschema.mytable. T held by
[user (Moveout: (Table: myschema.mytable) (Projection: myschema.mytable_b1))],
T held by [user <unknown> (Moveout: (Table: myschema.mytable)
(Projection: myschema.mytable_b0))].
Your current transaction isolation level is SERIALIZABLE;
Error while executing the query (7) (SQLExecDirectW)')
55V03 - zombie moveout process causing table insert to fail
Moderator: NorbertKrupa
Re: 55V03 - zombie moveout process causing table insert to f
Hi,
Try increase the moveout interval parameter, so that your moveout process starts at defined intervals according to you.
Are you trying to load data frequently? ( frequency less then 5 mins )
How are you checking the moveout process is running.
Try this SQL to check
If this shows the Moveout process is running then check whether it ends before the next moveout starts.
Hope this helps.
Try increase the moveout interval parameter, so that your moveout process starts at defined intervals according to you.
Are you trying to load data frequently? ( frequency less then 5 mins )
How are you checking the moveout process is running.
Try this SQL to check
Code: Select all
select * from system_sessions where is_active='t'
Hope this helps.
Re: 55V03 - zombie moveout process causing table insert to f
Check the tuple_mover_operations table (where is_executing) to see how long the moveout has been running, and what phase it’s in. If it’s a single long-running moveout, then changing the interval won’t help.
What version are you running?
—Sharon
What version are you running?
—Sharon
Sharon Cutter
Vertica Consultant, Zazz Technologies LLC
Vertica Consultant, Zazz Technologies LLC