[Question posted by a user on YugabyteDB Community Slack]
I'm loading data into one table and see this on tables view on web console
Total: 2.54G
Consensus Metadata: 154.7K
WAL Files: 15.00G
SST Files: -12.46G
SST Files Uncompressed: 4.00G
Why is there a negative value for SST Files?
YugabyteDB version is 2.6.7.0 in a single node database.
This was fixed in the 2.8 branch. Specifically this commit: https://github.com/yugabyte/yugabyte-db/commit/a8152fa9a98fce7eb37cd6c87244ed7bd29a5965
Related
[Question posted by a user on YugabyteDB Community Slack]
Is it possible to have the primary data cluster and read replica be at different versions?
primary data # 2.1 and replicate cluster # 2.8
Ideally, no. During software upgrades, temporarily different nodes can be on different releases. But in a steady state, the read-replica nodes should be the same version as the primary cluster.
With xCluster, where the two clusters are really independent clusters linked with an async replication channel, they can be on different releases for extended periods of time.
[Question posted by a user on YugabyteDB Community Slack]
Can somebody explain to me how to work with indexes metadata in YCQL?
I found this article: https://docs.yugabyte.com/preview/api/ycql/ddl_create_index/.
And I can't create example INDEX with WHERE condition with this exception:
com.datastax.driver.core.exceptions.SyntaxError: Feature Not Supported
CREATE INDEX idx ON orders (warehouse_id) WHERE warehouse_id < 100
^^^^^^
(ql error -14)
Server: YCQL 3.9.0
Driver: Yugabyte CQL Java Driver 3.8.2
YugabyteDB 2.4.4.0.
You need to upgrade to 2.6.x at a minimum to have that feature. After you upgrade you'll be able to create the index.
[Question posted by a user on YugabyteDB Community Slack]
I’m trying to understand the tolerance failure in YugabyteDB.
My scenario is as follows:
Universe is setup with primary data cluster and 1 read replica cluster, max_stale_read_bound_time_ms = 60.
And the primary data cluster got wipe out (lost all data).
Questions:
Would we be able to rebuild the primary data cluster with the read replica cluster?
Can the read replica cluster become the primary data cluster?
The answer is no to both.
xCluster is what you want to use for DR.
The design point for read-replicas in YugabyteDB is not for DR, but rather to bring data closer to where data is being read from. And read replicas have no yb-master. Without a yb-master, one cannot read from it.
[Question posted by a user on YugabyteDB Community Slack]
Is it possible to work with the Postgres tables using Spark-connector? Write and read to a Yugabyte Postgres?
Yes, it is possible to read and write in YugabyteDB through the JDBC Spark connector. You can follow the Spark documentation as is.
Because YugabyteDB is PostgreSQL-compliant most PostgreSQL connectors should work just fine.
[Question posted by a user on YugabyteDB Community Slack]
Is there a way to set wal_level = logical instead of replica in YugabyteDB? I’m looking to implement CDC so I can synchronize other systems with the changes.
Note that YugabyteDB doesn’t reuse the PostgreSQL storage engine & replication mechanism, but has built its own. And it doesn’t support setting wal_level=logical.
Currently, CDC support is in the works https://github.com/yugabyte/yugabyte-db/issues/9019.