yugabyte-db | cloud native distributed SQL database | Database library

A simple workaround is to make 2 dumps. The first one is just for the schema in text format.

Try importing it in PostgreSQL, see the errors and you can easily fix the DDL queries manually by removing HASH or special keywords that YugabyteDB uses.

Then take another dump, but this time just for the data which should be able to be imported in PostgreSQL.

Those are defaults and can be overwritten by the default_memory_limit_to_ram_ratio=0.1 flag. The idea is that if there's a master and tserver on the same node, we allow 10% to master, 85% to tserver (and remains 5% to system + PostgreSQL work_mem + filesystem buffers).

If you have a node that runs only the master, then clearly this should be changed. But usually, masters are started on the same nodes as tservers.

Each data file contains a reference to the key id of the master side key used to encrypt its file-level data key, so technically even after a master key rotation we may have older sst files which reference the old key. So if you want no older data files to reference the old key after a rotation, you will have to do a manual compaction.

This isn't yet supported. Can you create an issue on github https://github.com/yugabyte/yugabyte-db/issues ?

We are trying to reproduce this internally and will get back to you. In the meanwhile, could you please check the tserver.err file and the tserver.INFO logs (how to find yb-ctl tserver logs instructions) to see if anything bad is happening? Feels like the tservers are not up and running.

Download the db:

Hash partitioned table is specified as CREATE TABLE sample(k1 int, k2 int, PRIMARY KEY (k1, k2));

Setting the first column of the primary key as ASC/DESC will use range partitioning like:

CREATE TABLE sample(k1 int, k2 int, PRIMARY KEY (k1 ASC, k2 DESC));

Docs page for more info: https://docs.yugabyte.com/latest/api/ysql/commands/ddl_create_table/

Geo partitioned tables are not yet possible. You can subscribe to this issue: https://github.com/yugabyte/yugabyte-db/issues/1958

You are using a very old version of YugabyteDB. 2.0.10 is latest as of Jan 9 2020.

And looks like you have a path mismatch.Can you verify that the files are there and the build finished correctly ?

Download & install (https://download.yugabyte.com)the db: