ERROR 1218 (08S01): Error connecting to master: master is running an incompatible version of MemSQL

Issue

This issue can be caused when trying to replicate between a v5.x cluster and a v6.x cluster. Cluster replication functionality changes in 6.0 mean that replication between v5 and v6 is not possible. See Replication Compatibility Between Different Cluster Versions.

Solution

You need to upgrade both clusters to 6.0 before you can replicate data again. See Upgrading to 6.0 for more information. After both clusters are running 6.0 or newer, you can re-enabling replication between the clusters.

ERROR 1795: Cannot SHOW PARTITIONS. Database memsql is not sharded.

Issue

This error occurs when you attempt to backup the sharding or memsql databases.

Solution

These databases are internal system databases, and as such, they cannot and do not need to be backed up.

ERROR 1832 (HY000): Restoring partitions on %s. Couldn’t find backup file for partition # of database X (there are ### partitions without backup files).

Issue

This error means that there is not enough available disk in the backup directory.

Solution

Make sure that you have sufficient disk space in the designated backup directory and retry the operation.

ERROR: Partition’s table metadata are out of sync for table

Issue

The most common cause for this error is an ALTER TABLE query on a sharded table which ran partially but didn’t complete successfully. This may leave table metadata in an inconsistent state where some partitions have the old metadata while some have the new.

Solutions

If the cause of the issue was a failed ALTER TABLE as described above, possible solutions are:

• Recreate the table. This can be done by insert-selecting the data into a newly created table or reloading the data. For example:

  CREATE TABLE t_copy AS SELECT * FROM t; 
  DROP TABLE t; 
  ALTER TABLE t_copy RENAME AS t;
  

• Find the partition(s) with inconsistent table metadata, and manually run ALTER on the leaf partitions to correct them.

Transform for pipeline <pipeline_name> exited with ‘FAILURE’. Truncated stderr:

Issue

This is a general error code; however, this error can occur when your pipeline tries to execute your transform while loading your data into SingleStore DB. You will receive information in the stderr text informing you of the specific transform on the node that is failing. Transforms must be executable scripts, so your transform is likely missing a shebang at the top of the file.

Solution

Place a shebang at the top of your transform file to invoke the correct interpreter. This will depend on the programming language used in your transform and where the interpreter resides (e.g. #!/usr/bin/env python3 for Python 3 or #!/usr/bin/env ruby for Ruby).

Was this Article Helpful?

Thanks For Your Feedback!