diff --git a/_includes/v19.1/known-limitations/adding-stores-to-node.md b/_includes/v19.1/known-limitations/adding-stores-to-node.md new file mode 100644 index 00000000000..ee4844e2433 --- /dev/null +++ b/_includes/v19.1/known-limitations/adding-stores-to-node.md @@ -0,0 +1,5 @@ +After a node has initially joined a cluster, it is not possible to add additional [stores](start-a-node.html#store) to the node. Stopping the node and restarting it with additional stores causes the node to not reconnect to the cluster. + +To work around this limitation, [decommission the node](remove-nodes.html), remove its data directory, and then run [`cockroach start`](start-a-node.html) to join the cluster again as a new node. + +[Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/39415) diff --git a/_includes/v19.2/known-limitations/adding-stores-to-node.md b/_includes/v19.2/known-limitations/adding-stores-to-node.md new file mode 100644 index 00000000000..ee4844e2433 --- /dev/null +++ b/_includes/v19.2/known-limitations/adding-stores-to-node.md @@ -0,0 +1,5 @@ +After a node has initially joined a cluster, it is not possible to add additional [stores](start-a-node.html#store) to the node. Stopping the node and restarting it with additional stores causes the node to not reconnect to the cluster. + +To work around this limitation, [decommission the node](remove-nodes.html), remove its data directory, and then run [`cockroach start`](start-a-node.html) to join the cluster again as a new node. + +[Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/39415) diff --git a/_includes/v2.1/known-limitations/adding-stores-to-node.md b/_includes/v2.1/known-limitations/adding-stores-to-node.md new file mode 100644 index 00000000000..ee4844e2433 --- /dev/null +++ b/_includes/v2.1/known-limitations/adding-stores-to-node.md @@ -0,0 +1,5 @@ +After a node has initially joined a cluster, it is not possible to add additional [stores](start-a-node.html#store) to the node. Stopping the node and restarting it with additional stores causes the node to not reconnect to the cluster. + +To work around this limitation, [decommission the node](remove-nodes.html), remove its data directory, and then run [`cockroach start`](start-a-node.html) to join the cluster again as a new node. + +[Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/39415) diff --git a/_includes/v20.1/known-limitations/adding-stores-to-node.md b/_includes/v20.1/known-limitations/adding-stores-to-node.md new file mode 100644 index 00000000000..ee4844e2433 --- /dev/null +++ b/_includes/v20.1/known-limitations/adding-stores-to-node.md @@ -0,0 +1,5 @@ +After a node has initially joined a cluster, it is not possible to add additional [stores](start-a-node.html#store) to the node. Stopping the node and restarting it with additional stores causes the node to not reconnect to the cluster. + +To work around this limitation, [decommission the node](remove-nodes.html), remove its data directory, and then run [`cockroach start`](start-a-node.html) to join the cluster again as a new node. + +[Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/39415) diff --git a/v19.1/known-limitations.md b/v19.1/known-limitations.md index b423ffd0bf2..d85ea429bd7 100644 --- a/v19.1/known-limitations.md +++ b/v19.1/known-limitations.md @@ -8,6 +8,10 @@ This page describes newly identified limitations in the CockroachDB {{page.relea ## Unresolved limitations +### Adding stores to a node + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ### Cold starts of large clusters may require manual intervention If a cluster contains a large amount of data (>500GiB / node), and all nodes are stopped and then started at the same time, clusters can enter a state where they're unable to startup without manual intervention. In this state, logs fill up rapidly with messages like `refusing gossip from node x; forwarding to node y`, and data and metrics may become inaccessible. diff --git a/v19.1/start-a-node.md b/v19.1/start-a-node.md index 733dff444a4..fffb7306a67 100644 --- a/v19.1/start-a-node.md +++ b/v19.1/start-a-node.md @@ -188,6 +188,10 @@ Field | Description `clusterID` | The ID of the cluster.

When trying to join a node to an existing cluster, if this ID is different than the ID of the existing cluster, the node has started a new cluster. This may be due to conflicting information in the node's data directory. For additional guidance, see the [troubleshooting](common-errors.html#node-belongs-to-cluster-cluster-id-but-is-attempting-to-connect-to-a-gossip-network-for-cluster-another-cluster-id) docs. `nodeID` | The ID of the node. +## Known limitations + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ## Examples ### Start a single-node cluster diff --git a/v19.2/known-limitations.md b/v19.2/known-limitations.md index f9bfcbfa0a0..5c83b275dab 100644 --- a/v19.2/known-limitations.md +++ b/v19.2/known-limitations.md @@ -33,6 +33,10 @@ pq: check constraint violated ## Unresolved limitations +### Adding stores to a node + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ### Cold starts of large clusters may require manual intervention If a cluster contains a large amount of data (>500GiB / node), and all nodes are stopped and then started at the same time, clusters can enter a state where they're unable to startup without manual intervention. In this state, logs fill up rapidly with messages like `refusing gossip from node x; forwarding to node y`, and data and metrics may become inaccessible. diff --git a/v19.2/start-a-node.md b/v19.2/start-a-node.md index faab737fe94..2095ef8cca2 100644 --- a/v19.2/start-a-node.md +++ b/v19.2/start-a-node.md @@ -180,6 +180,10 @@ Field | Description `clusterID` | The ID of the cluster.

When trying to join a node to an existing cluster, if this ID is different than the ID of the existing cluster, the node has started a new cluster. This may be due to conflicting information in the node's data directory. For additional guidance, see the [troubleshooting](common-errors.html#node-belongs-to-cluster-cluster-id-but-is-attempting-to-connect-to-a-gossip-network-for-cluster-another-cluster-id) docs. `nodeID` | The ID of the node. +## Known limitations + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ## Examples ### Start a multi-node cluster diff --git a/v2.1/known-limitations.md b/v2.1/known-limitations.md index 8bbe1fdf6aa..b1118f46617 100644 --- a/v2.1/known-limitations.md +++ b/v2.1/known-limitations.md @@ -8,6 +8,10 @@ This page describes newly identified limitations in the CockroachDB {{page.relea ## New limitations +### Adding stores to a node + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ### Change data capture Change data capture (CDC) provides efficient, distributed, row-level change feeds into Apache Kafka for downstream processing such as reporting, caching, or full-text indexing. diff --git a/v2.1/start-a-node.md b/v2.1/start-a-node.md index 81e691213da..62d2e4dc55c 100644 --- a/v2.1/start-a-node.md +++ b/v2.1/start-a-node.md @@ -173,6 +173,10 @@ Field | Description `clusterID` | The ID of the cluster.

When trying to join a node to an existing cluster, if this ID is different than the ID of the existing cluster, the node has started a new cluster. This may be due to conflicting information in the node's data directory. For additional guidance, see the [troubleshooting](common-errors.html#node-belongs-to-cluster-cluster-id-but-is-attempting-to-connect-to-a-gossip-network-for-cluster-another-cluster-id) docs. `nodeID` | The ID of the node. +## Known limitations + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ## Examples ### Start a single-node cluster diff --git a/v20.1/known-limitations.md b/v20.1/known-limitations.md index 86c7be5c18c..581b1e15a40 100644 --- a/v20.1/known-limitations.md +++ b/v20.1/known-limitations.md @@ -8,6 +8,10 @@ This page describes newly identified limitations in the CockroachDB {{page.relea ## Unresolved limitations +### Adding stores to a node + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ### `CHECK` constraint validation for `INSERT ON CONFLICT` differs from PostgreSQL CockroachDB validates [`CHECK`](check.html) constraints on the results of [`INSERT ON CONFLICT`](insert.html#on-conflict-clause) statements, preventing new or changed rows from violating the constraint. Unlike PostgreSQL, CockroachDB does not also validate `CHECK` constraints on the input rows of `INSERT ON CONFLICT` statements. diff --git a/v20.1/start-a-node.md b/v20.1/start-a-node.md index 445ad019349..f6797dceb30 100644 --- a/v20.1/start-a-node.md +++ b/v20.1/start-a-node.md @@ -180,6 +180,10 @@ Field | Description `clusterID` | The ID of the cluster.

When trying to join a node to an existing cluster, if this ID is different than the ID of the existing cluster, the node has started a new cluster. This may be due to conflicting information in the node's data directory. For additional guidance, see the [troubleshooting](common-errors.html#node-belongs-to-cluster-cluster-id-but-is-attempting-to-connect-to-a-gossip-network-for-cluster-another-cluster-id) docs. `nodeID` | The ID of the node. +## Known limitations + +{% include {{ page.version.version }}/known-limitations/adding-stores-to-node.md %} + ## Examples ### Start a multi-node cluster