issues Search Results · repo:vitessio/vitess language:Go
Filter by
4k results
(86 ms)4k results
invitessio/vitess (press backspace or delete to remove)Overview of the Issue
It seems when we enable the flag above, we need to check server capabilities to make sure we can run ALTER INSTANCE
DISABLE INNODB REDO_LOG, but the validation fails because the ...
Needs Triage
Type: Bug
rvrangel
- Opened 1 hour ago
- #18309
Overview of the Issue
Ran into this bug running a query through vtgate, but was able to bypass it with individual shard targeting. The intent
of the query was to happen on individual shards, and I m guessing ...
Needs Triage
Type: Bug
derekperkins
- Opened yesterday
- #18308
Feature Description
This issue requests that the recoveries counters in VTOrc include a keyspace/shard, not just a global total. This is
useful for VTOrc deployments watching many shards
Use Case(s) ...
Component: Observability
Component: VTorc
Type: Enhancement
timvaillancourt
- Opened 2 days ago
- #18305
Overview of the Issue
We ve been seeing spikes in memory usage on our vtgates, sometimes leading to OOM kills of our vtgate pods due to a very
specific query pattern.
Basically, we re running large-ish ...
Component: Query Serving
Type: Bug
arthurschreiber
- Opened 7 days ago
- #18288
Feature Description
When on transaction_mode = single. If the application open more than one shard transaction. Vitess fails the query and
rollbacks the transaction. We should allow this for read-only ...
Component: Query Serving
Type: Enhancement
harshit-gangal
- Opened 7 days ago
- #18285
Overview of the Issue
We noticed a couple of failures in CREATE PROCEDURE statements (Support added in
https://github.com/vitessio/vitess/pull/17946) -
1. When a SET y = 4 statement is used, by the ...
Component: Query Serving
Type: Bug
GuptaManan100
- Opened 9 days ago
- #18278
Overview of the Issue
It has been noticed that sometimes the semi-sync monitor can deadlock.
The deadlock occurs with the following goroutines -
goroutine 66 [chan send]:
vitess.io/vitess/go/timer.(*Timer).Stop(0x1400060a270?) ...
Component: VTTablet
Type: Bug
- Opened 9 days ago
- #18275
Feature Description
The current vstream architecture is as follows:
- VTTablet
1. Reads the binlog
2. Serializes to protobuf
3. Sens the protobuf event to the VTGate
- VTGate
1. ...
Needs Triage
twthorn
- Opened 9 days ago
- #18273
Overview of the Issue
We recently run multiple times into a case where a vttablet would end up with an incredibly large number of goroutines
all stuck in the query consolidator code path:
goroutine profile: ...
Component: VTTablet
Type: Bug
- Opened 10 days ago
- #18272
Overview of the Issue
Using prepared statement, the following SQL (that s generated by our ORM Laravel/Eloquent) failed.
I thinks it s new and appears since v22.
Reproduction Steps
{
sharded : true, ...
Needs Triage
Type: Bug
L3o-pold
- Opened 11 days ago
- #18271
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.