If you need to log an issue with our support, please consider the following and try to get the relevant data into the ticket of your GitHub support request or have it handy when you are chatting with our support. This helps us to understand your request and determine the right steps and - in case of technical issues or questions - the root cause of the problem.

  • CrateDB version;

  • OS version / environment description;

  • Description of the problem: Please include relevant logs and error messages /stacktraces if possible;

  • Does it happen on peak (heavy load) or off-peak?

  • Steps to reproduce/sample records/queries etc.

Node Information can be provided with:

SELECT name,
       version['number'] AS crate_version,
       (mem['free'] + mem['used']) / 1024.0 / 1024.0 / 1024.0 AS memory_gb,
       heap['max'] / 1024.0 / 1024.0 / 1024.0 AS heap_size_gb,
       fs['total']['size'] / 1024.0 / 1024.0 / 1024.0 AS disk_size_gb,
       process['max_open_file_descriptors'] AS max_open_files,
       os_info['available_processors'] AS cpus,
       format('%s %s %s; %s',
         os_info['name'],
         hostname,
         os_info['version'],
         os_info['arch']) AS uname,
       format('Java %s %s %s (build %s)',
         os_info['jvm']['version'],
         os_info['jvm']['vm_vendor'],
         os_info['jvm']['vm_name'],
         os_info['jvm']['vm_version']) as jvm
FROM sys.nodes
ORDER BY 1;

If a certain table is affected you can run this query to provide us detailed shard information: INFO: Replace the ? placeholder with the table name.

SELECT schema_name || '.' || table_name AS "table",
       COUNT(*) as shards,
       CAST(SUM(num_docs) AS LONG) as docs,
       CAST(SUM(size) AS LONG) as size
FROM sys.shards
WHERE "primary" = true AND table_name = ?
GROUP BY 1 ORDER BY 1;

Did this answer your question?