vitessio/vitess · error

GetVSchema(%s) failed: %v

Error message

GetVSchema(%s) failed: %v

What it means

Returned by the grpcvtctldserver GetVSchema handler when reading the vschema for the given keyspace from the topology fails, wrapping the underlying error.

Source

Thrown at go/vt/vtctl/grpcvtctldserver/server.go:5468

	}

	return &response, nil
}

// ValidateVSchema compares the schema of each primary tablet in "keyspace/shards..." to the vschema and errs if there are differences
func (s *VtctldServer) ValidateVSchema(ctx context.Context, req *vtctldatapb.ValidateVSchemaRequest) (resp *vtctldatapb.ValidateVSchemaResponse, err error) {
	span, ctx := trace.NewSpan(ctx, "VtctldServer.ValidateVSchema")
	defer span.Finish()

	defer panicHandler(&err)
	keyspace := req.Keyspace
	shards := req.Shards
	excludeTables := req.ExcludeTables
	includeViews := req.IncludeViews

	vschm, err := s.ts.GetVSchema(ctx, keyspace)
	if err != nil {
		err = fmt.Errorf("GetVSchema(%s) failed: %v", keyspace, err)
		return nil, err
	}

	resp = &vtctldatapb.ValidateVSchemaResponse{
		Results:        []string{},
		ResultsByShard: make(map[string]*vtctldatapb.ValidateShardResponse, len(shards)),
	}

	var (
		wg sync.WaitGroup
		m  sync.Mutex
	)

	wg.Add(len(shards))

	for _, shard := range shards {
		go func(shard string) {
			defer wg.Done()

View on GitHub (pinned to 01a25a7d17)

Solutions

1. Check the keyspace name against vtctldclient GetKeyspaces.
2. Apply a VSchema: vtctldclient ApplyVSchema --vschema-file vschema.json <keyspace>.
3. Verify topo connectivity if the keyspace is known to have a VSchema.

Example fix

// before (no vschema yet)
vtctldclient ValidateVSchema commerce
// after
vtctldclient ApplyVSchema --vschema-file vschema.json commerce
vtctldclient ValidateVSchema commerce

vs, err := ts.GetVSchema(ctx, keyspace); if topo.IsErrType(err, topo.NoNode) { return fmt.Errorf("keyspace %s has no VSchema; run ApplyVSchema first", keyspace) }

_, err := ts.GetVSchema(ctx, ks); if topo.IsErrType(err, topo.NoNode) { /* apply a default vschema or abort */ }

When it happens

Trigger: ValidateVSchema called for a keyspace with no VSchema entry in the topo, or the topo read itself fails.

Common situations: Typo in keyspace name; keyspace created but ApplyVSchema never run; topo backend unavailable.

Related errors

• SrvVSchema has no entry for keyspace %v
• BaseKeyspace is required for SNAPSHOT keyspaces
• SnapshotTime is required for SNAPSHOT keyspaces
• no shards found in keyspace
• a POST request needs a keyspace in the URL

AI-assisted analysis of vitessio/vitess@01a25a7d17 (2026-09-01). Data as JSON: /api/errors/fd29c3828e0ddfee. Report an issue: GitHub.