Skip to content

Commit

Permalink
[docs] fix a few 404s (#9474)
Browse files Browse the repository at this point in the history
  • Loading branch information
Alex Ball authored Jul 28, 2021
1 parent 0ae28f6 commit ff06e87
Show file tree
Hide file tree
Showing 4 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -112,4 +112,4 @@ thirdparty/
submodules/

# Local Netlify folder
.netlify
.netlify/
2 changes: 1 addition & 1 deletion docs/content/latest/releases/earlier-releases/v2.1.8.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ admin/yb-admin/#master-leader-stepdown) command. [#4135](https://github.com/yuga
- When creating GCP instances, only use host project when specifying network.
- When creating a cloud provider configuration, display provider-level (non-k8s) settings for SSH ports and enabling airgapped installations. [#3615](https://github.com/yugabyte/yugabyte-db/issues/3615), [#4243](https://github.com/yugabyte/yugabyte-db/issues/4243), and [#4240](https://github.com/yugabyte/yugabyte-db/issues/4240).
- After removing a node and then adding a node, check for certificate and key files and create the files if needed. [#4551](https://github.com/yugabyte/yugabyte-db/issues/4551)
- Update to support Helm 3 deployments. Note: Helm 2 is no longer supported. For migrating existing Helm 2 universes to Helm 3, see [Migrate from Helm 2 to Helm 3](../../../yugabyte-platform/manage-deployments/migrate-to-helm3/). [#4416]((https://github.com/yugabyte/yugabyte-db/issues/4416))
- Update to support Helm 3 deployments. Note: Helm 2 is no longer supported. For migrating existing Helm 2 universes to Helm 3, see [Migrate from Helm 2 to Helm 3](../../../yugabyte-platform/manage-deployments/migrate-to-helm3/). [#4416](https://github.com/yugabyte/yugabyte-db/issues/4416)
- Change `QLTableRow` representation. [#4427](https://github.com/yugabyte/yugabyte-db/issues/4427)
- Fix CDC-related race conditions using `CDCServiceTxnTest.TestGetChangesForPendingTransaction`. [#4544](https://github.com/yugabyte/yugabyte-db/issues/4544)
- Revert validation on alerting email field to allow comma-separated emails in the form. [#4639](https://github.com/yugabyte/yugabyte-db/issues/4639)
Expand Down
2 changes: 1 addition & 1 deletion docs/content/v1.3/introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ YugabyteDB supports two flavors of distributed SQL.

### 2. Yugabyte Cloud QL (YCQL)

[YCQL]((../api/ycql/)) is a SQL-based flexible-schema API that is best fit for internet-scale OLTP apps needing a semi-relational API highly optimized for write-intensive applications as well as blazing-fast queries. It supports distributed transactions, strongly consistent secondary indexes and a native JSON column type. YCQL has its roots in the Cassandra Query Language. Get started by [exploring YCQL features](../api/ycql/quick-start/).
[YCQL](../api/ycql/) is a SQL-based flexible-schema API that is best fit for internet-scale OLTP apps needing a semi-relational API highly optimized for write-intensive applications as well as blazing-fast queries. It supports distributed transactions, strongly consistent secondary indexes and a native JSON column type. YCQL has its roots in the Cassandra Query Language. Get started by [exploring YCQL features](../api/ycql/quick-start/).

{{< note title="Note" >}}
The YugabyteDB APIs are isolated and independent from one another today. This means that the data inserted or managed by one API cannot be queried by the other API. Additionally, there is no common way to access the data across the APIs (external frameworks such as [Presto](../develop/ecosystem-integrations/presto/) can help for simple cases).
Expand Down
4 changes: 2 additions & 2 deletions docs/content/v2.0/deploy/multi-dc/3dc-deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Follow the [installation instructions](../../../deploy/manual-deployment/install

## 2. Start YB-Masters

Run the `yb-master` server on each of the nodes as shown below. Note how multiple directories can be provided to the `--fs_data_dirs` option. Replace the [`--rpc_bind_addresses`]((../../../reference/configuration/yb-master/#rpc-bind-addresses) value with the private IP address of the host as well as the set the `--placement_cloud`,`--placement_region` and `--placement_zone` values appropriately.
Run the `yb-master` server on each of the nodes as shown below. Note how multiple directories can be provided to the `--fs_data_dirs` option. Replace the [`--rpc_bind_addresses`](../../../reference/configuration/yb-master/#rpc-bind-addresses) value with the private IP address of the host as well as the set the `--placement_cloud`,`--placement_region` and `--placement_zone` values appropriately.

```sh
$ ./bin/yb-master \
Expand All @@ -54,7 +54,7 @@ $ ./bin/yb-master \
>& /home/centos/disk1/yb-master.out &
```

Note that we also set the [`--leader_failure_max_missed_heartbeat_periods`](../../../reference/configuration/yb-master/#leader-failure-max-missed-heartbeat-periods) option to `10`. This option specifies the maximum heartbeat periods that the leader can fail to heartbeat before the leader is considered to be failed. Since the data is geo-replicated across data centers, RPC latencies are expected to be higher. We use this flag to increase the failure detection interval in such a higher RPC latency deployment. Note that the total failure timeout is now 5 seconds since it is computed by multiplying [`--raft_heartbeat_interval_ms`](../../../reference/configuration/yb-master/#raft-heartbeat-interval-ms) (default of 500ms) with [`--leader_failure_max_missed_heartbeat_periods`]((../../../reference/configuration/yb-master/#leader-failure-max-missed-heartbeat-periods) (current value of `10`).
Note that we also set the [`--leader_failure_max_missed_heartbeat_periods`](../../../reference/configuration/yb-master/#leader-failure-max-missed-heartbeat-periods) option to `10`. This option specifies the maximum heartbeat periods that the leader can fail to heartbeat before the leader is considered to be failed. Since the data is geo-replicated across data centers, RPC latencies are expected to be higher. We use this flag to increase the failure detection interval in such a higher RPC latency deployment. Note that the total failure timeout is now 5 seconds since it is computed by multiplying [`--raft_heartbeat_interval_ms`](../../../reference/configuration/yb-master/#raft-heartbeat-interval-ms) (default of 500ms) with [`--leader_failure_max_missed_heartbeat_periods`](../../../reference/configuration/yb-master/#leader-failure-max-missed-heartbeat-periods) (current value of `10`).

For the full list of configuration options, see the [YB-Master reference](../../../reference/configuration/yb-master/).

Expand Down

0 comments on commit ff06e87

Please sign in to comment.