-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow redis reads from followers #110
Labels
kind/enhancement
This is an enhancement of an existing feature
Comments
rkarthik007
added
the
kind/enhancement
This is an enhancement of an existing feature
label
Apr 3, 2018
yugabyte-ci
pushed a commit
that referenced
this issue
Apr 8, 2018
Summary: Created a new flag to allow reads from followers. Internally, we select a tserver using SelectTabletServerWithConsistentPrefix which selects the closest tserver in the same AZ. Test Plan: Ran a redis workload in a real cluster (AWS, 3 nodes, multi-AZ) With the flag set to false (default): Avg. latency with 2 reader threads: 0.84 ms With the flag set to true: Avg. latency with 2 reader threads: .17 ms Reviewers: karthik, mikhail, kannan, pritam.damania Reviewed By: pritam.damania Subscribers: amitanand, ybase Differential Revision: https://phabricator.dev.yugabyte.com/D4457
Ran a redis workload in a real cluster (AWS, 3 nodes, multi-AZ) |
mbautin
pushed a commit
that referenced
this issue
Jun 20, 2019
skorobogatydmitry
added a commit
that referenced
this issue
Dec 22, 2020
Summary: - /customers - list of customers to make respective requests on some particular customer - /api/index - list API endpoints to discover available methods Test Plan: 1. ``` curl --header 'X-AUTH-TOKEN: ...' http://localhost:9000/api/index | python -m json.tool curl --header 'X-AUTH-TOKEN: ...' http://localhost:9000/api/v1/index | python -m json.tool ``` 2. ``` curl --header 'X-AUTH-TOKEN: ...' http://localhost:9000/api/v1/customers | python -m json.tool curl --header 'X-AUTH-TOKEN: ...' http://localhost:9000/api/customers | python -m json.tool ``` Reviewers: sanketh, arnav, spotachev Reviewed By: spotachev Subscribers: jenkins-bot Differential Revision: https://phabricator.dev.yugabyte.com/D10185
tvesely
pushed a commit
to tvesely/yugabyte-db
that referenced
this issue
Feb 28, 2024
This commit fixes and extends the extension SQL scripts in a few ways, to allow upgrades from all the possible versions down where the origin is based on PostgreSQL 10, which is the oldest version supported by pg_hint_plan currently. PostgreSQL allows since v10 the maintenance of an extension using as base script the oldest version supported in combination of incremental scripts. A full set of upgrade scripts is added by this commit, considering v10 as the oldest path supported. As origin versions may have a partial schema created for the hint table with partial definitions, the correct rules are enforced for each version when it comes to extension dumps and GRANT rules. The schema for the hint table is only created in the base script. Regression tests are added to cover all these upgrade paths. DATA in the Makefile is changed to hardcode all the SQL scripts that need to be installed. Per pull request yugabyte#111 and issues yugabyte#110 and yugabyte#60. Backpatch-through: 10
jasonyb
pushed a commit
that referenced
this issue
Jun 11, 2024
PG-227: Enable PGSM master branch regression/test with latest PG releases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add a new tserver gflag.
When the flag is enabled for the tservers, it will allow the tserver's query layer to route a Redis read request to any tserver within the same DC/region/AZ even if that tserver is not the leader.
The text was updated successfully, but these errors were encountered: