ROSSALColumnAccess position not found Error!

[sarah]

Hi all,

This morning I had a node drop from my test cluster. Below are the errors from the dc_errors table... Can someone let me know what the "ROSSALColumnAccess position not found" error indicates?

Code: Select all

dbadmin=> select time, function_name, log_message, error_level_name from dc_errors where time <= '2015-08-07 05:00:16' and node_name = 'v_test_node0002' and error_level_name = 'PANIC' order by time desc;
             time              | function_name |              log_message              | error_level_name
-------------------------------+---------------+---------------------------------------+------------------
 2015-08-07 04:16:40.255961-04 | goToPosition  | ROSSALColumnAccess position not found | PANIC
 2015-08-07 04:16:40.182487-04 | goToPosition  | ROSSALColumnAccess position not found | PANIC
(2 rows)

[NorbertKrupa]

Is this being called by a function? ROSSALColumnAccess isn't coming up in anything Vertica.

[scutter]

That’s vertica trying to find a particular “position” (row number) in a ROS and not finding it. Sounds like something got corrupted. Does the log file tell you which projection is corrupted?

—Sharon

[sarah]

Thanks for your replies.

#scutter, do you think this might be related to using san storage? Would Vertica go down if it loses contact with the storage temporarily?

[scutter]

Certainly. Vertica relies on keeping all nodes consistent. If a node can’t remain consistent (such as COMMITing a transaction), then it will take itself out of the cluster.

—Sharon