Remove tribe node support

buildSrc/src/main/resources/checkstyle_suppressions.xml

@@ -417,7 +417,6 @@
   <suppress files="server[/\\]src[/\\]main[/\\]java[/\\]org[/\\]elasticsearch[/\\]snapshots[/\\]SnapshotShardsService.java" checks="LineLength" />
   <suppress files="server[/\\]src[/\\]main[/\\]java[/\\]org[/\\]elasticsearch[/\\]snapshots[/\\]SnapshotsService.java" checks="LineLength" />
   <suppress files="server[/\\]src[/\\]main[/\\]java[/\\]org[/\\]elasticsearch[/\\]threadpool[/\\]ThreadPool.java" checks="LineLength" />
-  <suppress files="modules[/\\]tribe[/\\]src[/\\]main[/\\]java[/\\]org[/\\]elasticsearch[/\\]tribe[/\\]TribeService.java" checks="LineLength" />
   <suppress files="server[/\\]src[/\\]test[/\\]java[/\\]org[/\\]apache[/\\]lucene[/\\]queries[/\\]BlendedTermQueryTests.java" checks="LineLength" />
   <suppress files="server[/\\]src[/\\]test[/\\]java[/\\]org[/\\]elasticsearch[/\\]VersionTests.java" checks="LineLength" />
   <suppress files="server[/\\]src[/\\]test[/\\]java[/\\]org[/\\]elasticsearch[/\\]action[/\\]RejectionActionIT.java" checks="LineLength" />

docs/reference/modules.asciidoc

@@ -73,10 +73,6 @@ The modules in this section are:
     Configure the transport networking layer, used internally by Elasticsearch
     to communicate between nodes.
 
-<<modules-tribe,Tribe nodes>>::
-
-    A tribe node joins one or more clusters and acts as a federated
-    client across them.
 
 <<modules-cross-cluster-search, Cross cluster Search>>::
 

docs/reference/modules/cross-cluster-search.asciidoc

@@ -2,8 +2,8 @@
 == Cross Cluster Search
 
 The _cross cluster search_ feature allows any node to act as a federated client across
-multiple clusters. In contrast to the <<modules-tribe,tribe node>> feature, a  cross cluster search node won't
-join the remote cluster, instead it connects to a remote cluster in a light fashion in order to execute
+multiple clusters. A cross cluster search node won't join the remote cluster, instead
+it connects to a remote cluster in a light fashion in order to execute
 federated search requests.
 
 Cross cluster search works by configuring a remote cluster in the cluster state and connecting only to a

docs/reference/modules/network.asciidoc

@@ -171,9 +171,8 @@ settings, but may be further configured independently:
 TCP Transport::
 
 Used for communication between nodes in the cluster, by the Java
-{javaclient}/transport-client.html[Transport client] and by the
-<<modules-tribe,Tribe node>>.  See the <<modules-transport,Transport module>>
-for more information.
+{javaclient}/transport-client.html[Transport client].
+See the <<modules-transport,Transport module>> for more information.
 
 HTTP::
 

docs/reference/modules/node.asciidoc

@@ -35,17 +35,6 @@ and enrich the document before indexing. With a heavy ingest load, it makes
 sense to use dedicated ingest nodes and to mark the master and data nodes as
 `node.ingest: false`.
 
-<<modules-tribe,Tribe node>>::
-
-A tribe node, configured via the `tribe.*` settings, is a special type  of
-coordinating only node that can connect to multiple clusters and perform
-search and other operations across all connected clusters.
-
-By default a node is a master-eligible node and a data node, plus it can
-pre-process documents through ingest pipelines. This is very convenient for
-small clusters but, as the cluster grows, it becomes important to consider
-separating dedicated master-eligible nodes from dedicated data nodes.
-
 [NOTE]
 [[coordinating-node]]
 .Coordinating node

docs/reference/release-notes/7.0.0-alpha1.asciidoc

@@ -7,4 +7,5 @@ The changes listed below have been released for the first time in Elasticsearch
 [float]
 === Breaking changes
 
-No breaking changes have been made (yet)
+Core::
+* Tribe node has been removed in favor of Cross-Cluster-Search