Closed chinhtranvan closed 9 months ago
After trying kubectl get vrpq
with this change, I obtained this information
NAME AGE MESSAGE
vc 10s Query has completed successfully
For e2e test case verify server logrotate, it appears to include 'editor.log' for rotation. Prior to that, it only performs log rotation for 'vertica.log'
node_name | success | max_size | max_age | log_file | need_rotation
-------------------+---------+-----------+---------+-----------------------------------------------------------------------+---------------
v_vertdb_node0001 | t | 104857600 | 7 | /data/vertdb/v_vertdb_node0001_catalog/vertica.log | f
v_vertdb_node0001 | t | 104857600 | 7 | /data/vertdb/v_vertdb_node0001_catalog/UDxLogs/UDxFencedProcesses.log | f
v_vertdb_node0001 | t | 104857600 | 7 | /data/vertdb/v_vertdb_node0001_catalog/editor.log | f
v_vertdb_node0001 | t | 1024 | 7 | /data/vertdb/v_vertdb_node0001_catalog/vertica.log | t
v_vertdb_node0001 | t | 1024 | 7 | /data/vertdb/v_vertdb_node0001_catalog/UDxLogs/UDxFencedProcesses.log | f
v_vertdb_node0001 | t | 1024 | 7 | /data/vertdb/v_vertdb_node0001_catalog/editor.log | t
(6 rows)
I test with my local machine , it run successfuly and don't include editor.log. I add the new change to fix the e2e test in this PR
This PR adds custom print columns for the new VerticaRestorePointsQuery CR, so that a kubectl get vrpq command tells you if the query has completed.