Skip to content

Fix 404 not found #4750

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.

Sign up for GitHub

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

Merged
deepthi merged 1 commit into from
Mar 27, 2019
Merged

Fix 404 not found #4750

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions doc/GitHubWorkflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,8 +116,7 @@ After this change, you can run `git push` without arguments:

Then go to the [repository page](https://github.com/vitessio/vitess) and it
should prompt you to create a Pull Request from a branch you recently pushed.
You can also [choose a branch manually]
(https://github.com/vitessio/vitess/compare).
You can also [choose a branch manually](https://github.com/vitessio/vitess/compare).

## Addressing Changes

Expand Down
6 changes: 3 additions & 3 deletions doc/ReplicatoinLagBasedThrottlingOfTransactions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ feature is turned on, each VTTablet master monitors the replication lag from
the replicas, and based on the observed replication lag tries to rate-limit the
received transactions to keep the replication lag under a configured limit.

The decision of whether to throttle a transaction is done in the "BEGIN"
statement rather than in the "COMMIT" statement to avoid having a transaction
The decision of whether to throttle a transaction is done in the `BEGIN`
statement rather than in the `COMMIT` statement to avoid having a transaction
perform a lot of work just to eventually be throttled and potentially
rolled-back if the open-transaction timeout is exceeded.

Expand Down Expand Up @@ -38,5 +38,5 @@ the replication lag under the desired limit; as such the desired replication
lag limit may occasionally be slightly violated.

* Transactions are considered homogenous. There is currently no support
for specifying how "expensive" a transaction is.
for specifying how `expensive` a transaction is.

2 changes: 1 addition & 1 deletion doc/ScalabilityPhilosophy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ run it on baremetal configs, and many users still do. If deploying in a cloud,
the assignment of servers and ports is abstracted away from the administrator.
On baremetal, the operator still has these responsibilities.

We provide sample configs to help you [get started on Kubernetes](/getting-started/)
We provide sample configs to help you [get started on Kubernetes](https://vitess.io/docs/tutorials/kubernetes/)
since it's the most similar to Borg (the [predecessor to Kubernetes](https://kubernetes.io/blog/2015/04/borg-predecessor-to-kubernetes/)
on which Vitess now runs in YouTube).
If you're more familiar with alternatives like Mesos, Swarm, Nomad, or DC/OS,
Expand Down
4 changes: 2 additions & 2 deletions doc/ServerConfiguration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ Vitess servers are written in Go. There are a few Vitess-specific knobs that app

Go, being a young language, tends to add major improvements over each version.
So, the latest Go version is almost always recommended.
Note that the latest Go version may be higher than the minimum version we require for compiling the binaries (see ["Prerequisites" section in the Getting Started guide](/getting-started/#prerequisites)).

@xichengliudui xichengliudui Mar 25, 2019

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

404 not found

Note that the latest Go version may be higher than the minimum version we require for compiling the binaries (see ["Prerequisites" section in the Getting Started guide](https://github.com/vitessio/website/blob/master/content/docs/tutorials/kubernetes.md#prerequisites)).

### GOMAXPROCS

Expand Down Expand Up @@ -621,7 +621,7 @@ pretty much
[set up Orchestrator](https://github.com/github/orchestrator/wiki/Orchestrator-Manual)
in the normal way, with just a few additions as described below.

For the [Kubernetes example](/getting-started/), we provide a

@xichengliudui xichengliudui Mar 25, 2019

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

404 not found

For the [Kubernetes example](https://github.com/vitessio/website/blob/master/content/docs/tutorials/kubernetes.md), we provide a
[sample script](https://github.com/vitessio/vitess/blob/master/examples/kubernetes/orchestrator-up.sh)
to launch Orchestrator for you with these settings applied.

Expand Down
2 changes: 1 addition & 1 deletion doc/TwoPhaseCommitDesign.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ This document intends to address the above concerns with some practical trade-of

Although MySQL supports the XA protocol, it’s been unusable due to bugs. Version 5.7 claims to have fixed them all, but the more common versions in use are 5.6 and below, and we need to make 2PC work for those versions also. Even at 5.7, we still have to contend with the chattiness of XA, and the fact that it’s unused code.

The most critical component of the 2PC protocol is the ‘Prepare’ functionality. There is actually a way to implement Prepare on top of a transactional system. This is explained in a [Vitess Blog](https://vitess.io/blog/2016-06-07-distributed-transactions-in-vitess/), which will be used as foundation for this design.
The most critical component of the 2PC protocol is the `Prepare` functionality. There is actually a way to implement Prepare on top of a transactional system. This is explained in a [Vitess Blog](https://vitess.io/blog/2016-06-07-distributed-transactions-in-vitess/), which will be used as foundation for this design.

Familiarity with the blog and the [2PC algorithm](http://c2.com/cgi/wiki?TwoPhaseCommit) are required to understand the rest of the document.

Expand Down