Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
title: Move cluster concepts into Getting Started in Ref Guide
type: changed
authors:
- name: Eric Pugh
links:
- name: SOLR-18179
url: https://issues.apache.org/jira/browse/SOLR-18179
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ The Files screen in the Admin UI lets you browse & view configuration files (suc
.The Files Screen
image::configuration-files/files-screen.png[Files screen,height=400]

If you are using xref:deployment-guide:cluster-types.adoc#solrcloud-mode[SolrCloud], the files displayed are the configuration files for this collection stored in ZooKeeper.
If you are using xref:getting-started:cluster-types.adoc#solrcloud-mode[SolrCloud], the files displayed are the configuration files for this collection stored in ZooKeeper.
In user-managed clusters or single-node installations, all files in the `conf` directory are displayed.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lets use "standalone" instead of "single-node" installations.


The configuration files shown may or may not be used by the collection as use of the file depends on how they are referenced in either `solrconfig.xml` or your schema.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@
// specific language governing permissions and limitations
// under the License.

The Core Admin API is primarily used under the covers by the xref:collections-api.adoc[] when running a xref:deployment-guide:cluster-types.adoc#solrcloud-mode[SolrCloud] cluster.
The Core Admin API is primarily used under the covers by the xref:collections-api.adoc[] when running a xref:getting-started:cluster-types.adoc#solrcloud-mode[SolrCloud] cluster.

SolrCloud users should not typically use the CoreAdmin API directly, but the API may be useful for users of user-managed clusters or single-node installations for core maintenance operations.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,6 @@
*** xref:docker-faq.adoc[]

* Scaling Solr
** xref:cluster-types.adoc[]
** SolrCloud Clusters
*** xref:solrcloud-shards-indexing.adoc[]
*** xref:solrcloud-recoveries-and-write-tolerance.adoc[]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ This screen provides status information about each collection & node in your clu
.Only Visible When using SolrCloud
[NOTE]
====
The "Cloud" menu option is only available when Solr is running xref:cluster-types.adoc#solrcloud-mode[SolrCloud].
The "Cloud" menu option is only available when Solr is running xref:getting-started:cluster-types.adoc#solrcloud-mode[SolrCloud].
User-managed clusters or single-node installations will not display this option.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

again; use "standalone"

====

Expand Down
113 changes: 0 additions & 113 deletions solr/solr-ref-guide/modules/deployment-guide/pages/cluster-types.adoc

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ A very good blog post that discusses the issues to consider is https://lucidwork

One thing to note when planning your installation is that a hard limit exists in Lucene for the number of documents in a single index: approximately 2.14 billion documents (2,147,483,647 to be exact).
In practice, it is highly unlikely that such a large number of documents would fit and perform well in a single index, and you will likely need to distribute your index across a cluster before you ever approach this number.
If you know you will exceed this number of documents in total before you've even started indexing, it's best to plan your installation with xref:cluster-types.adoc#solrcloud-mode[SolrCloud] as part of your design from the start.
If you know you will exceed this number of documents in total before you've even started indexing, it's best to plan your installation with xref:getting-started:cluster-types.adoc#solrcloud-mode[SolrCloud] as part of your design from the start.

== Package Installation

Expand Down Expand Up @@ -197,7 +197,7 @@ Currently, the available examples you can run are: techproducts, schemaless, and
See the section xref:solr-control-script-reference.adoc#running-with-example-configurations[Running with Example Configurations] for details on each example.

.Going deeper with SolrCloud
NOTE: Running the `cloud` example demonstrates running multiple nodes of Solr using xref:cluster-types.adoc#solrcloud-mode[SolrCloud] mode.
NOTE: Running the `cloud` example demonstrates running multiple nodes of Solr using xref:getting-started:cluster-types.adoc#solrcloud-mode[SolrCloud] mode.
For more information on starting Solr in SolrCloud mode, see the section xref:getting-started:tutorial-solrcloud.adoc[].

=== Check if Solr is Running
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -339,7 +339,7 @@ For more information about starting Solr in SolrCloud mode, see also the section

`bin/solr start --user-managed` starts Solr in User Managed mode (AKA Standalone mode). This was the default mode up until Solr 10x.

For more information about the different modes, see the section xref:deployment-guide:cluster-types.adoc[].
For more information about the different modes, see the section xref:getting-started:cluster-types.adoc[].


==== Running with Example Configurations
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@

When using traditional index sharding, you will need to consider how to query your documents.

It is highly recommended that you use xref:cluster-types.adoc#solrcloud-mode[SolrCloud] when needing to scale up or scale out.
It is highly recommended that you use xref:getting-started:cluster-types.adoc#solrcloud-mode[SolrCloud] when needing to scale up or scale out.
The setup described below is legacy and was used prior to the existence of SolrCloud.
SolrCloud provides for a truly distributed set of features with support for things like automatic routing, leader election, optimistic concurrency and other sanity checks that are expected out of a distributed system.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Configuring replication is therefore similar to any normal request handler.
.Replication In SolrCloud
[NOTE]
====
Although there is no explicit concept of leader or follower nodes in a xref:cluster-types.adoc#solrcloud-mode[SolrCloud cluster], the `ReplicationHandler` discussed on this page is still used by SolrCloud as needed to support "shard recovery" – but this is done in a peer to peer manner.
Although there is no explicit concept of leader or follower nodes in a xref:getting-started:cluster-types.adoc#solrcloud-mode[SolrCloud cluster], the `ReplicationHandler` discussed on this page is still used by SolrCloud as needed to support "shard recovery" – but this is done in a peer to peer manner.

When using SolrCloud, the `ReplicationHandler` must be available via the `/replication` path.
Solr does this implicitly unless overridden explicitly in your `solrconfig.xml`.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@
** xref:solr-indexing.adoc[]
** xref:searching-in-solr.adoc[]
** xref:relevance.adoc[]
** xref:cluster-types.adoc[]
** xref:solr-glossary.adoc[]

* xref:solr-tutorial.adoc[]
Expand Down
Loading
Loading