Matt Lord

Hi @wiebeytec, Can you please provide a test case demonstrating this with [the local examples](https://github.com/vitessio/vitess/tree/main/examples/local)? It should be relatively easy to do given the same basic process you showed here....

Hi @wiebeytec , When implementing this `show vitess_replication_status` command I used the tablet's replication lag stats variable (managed within the discover package's tablet healthcheck) instead of the `seconds_behind_[master|source]` value from...

@kazablock what feature are you referring to? I think that this should be closed as it’s not clear. The unified stream that was previously mentioned exists: https://vitess.io/docs/reference/vreplication/vstream/

@timvaillancourt do you mind creating a real quick issue as well for this? 🙏

@GenLN the output does not show that the `mysqlbinlog` binary could not be found. It shows that it WAS found, and it was in fact it was `mysqlbinlog` that returned...

The xtrabackupengine uses the `tmpdir` value in the `my.cnf` file: https://github.com/vitessio/vitess/blob/main/go/vt/mysqlctl/xtrabackupengine.go https://dev.mysql.com/doc/refman/8.0/en/temporary-files.html That defaults to `/tmp`. You could change that to `/vt/tmp` here in your cluster definition: https://github.com/planetscale/vitess-operator/blob/main/docs/api.md#mysqldspec

Ah, I see: https://github.com/vitessio/vitess/blob/46975b20fa6b9dd77dc666cedded8b8f16bc757a/go/vt/mysqlctl/builtinbackupengine.go#L1008-L1013 That's the only place that the `restore-incremental` string literal is used.

One other note, I think that we should backport this to v18 if possible. I say that as that's when `vtctldclient Reshard` was added.

/cc @vitessio/query-serving

Is this still an issue on main? I thought that we had fixed this, but perhaps not.