This is an automated email from the ASF dual-hosted git repository.
oleewere pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ambari.git
The following commit(s) were added to refs/heads/trunk by this push:
new e11bab6 AMBARI-23945. Embed migration config generation steps to
README.md
e11bab6 is described below
commit e11bab6b4247d3e957f1104679ccb9f6d98a7ef9
Author: Olivér Szabó <[email protected]>
AuthorDate: Thu Jun 14 13:46:03 2018 +0200
AMBARI-23945. Embed migration config generation steps to README.md
---
ambari-infra/ambari-infra-solr-client/README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/ambari-infra/ambari-infra-solr-client/README.md
b/ambari-infra/ambari-infra-solr-client/README.md
index f40aa5c..5ba76e5 100644
--- a/ambari-infra/ambari-infra-solr-client/README.md
+++ b/ambari-infra/ambari-infra-solr-client/README.md
@@ -144,6 +144,8 @@ history_collection_name = history
After the file has created successfully by the script, review the
configuration (e.g.: if 1 of the Solr is not up yet, and you do not want to use
its REST API for operations, you can remove its url from the urls of infra_solr
section or you can change backup locations for different collections etc.)
+[](https://asciinema.org/a/xsdPY8wReNJwFfqU9t5FtLWeR?speed=2)
+
### <a id="ii.-backup-collections-(ambari-2.6.x-to-ambari-2.7.x)">III. Backup
collections (Ambari 2.6.x to Ambari 2.7.x)</a>
Before you start to upgrade process check the Solr instances are running and
also make sure you have stable shards (at least one core is up and running) and
will have enough space on the disks to store Solr backup data. (you will need
at least that many as your index size per host). The backup process contains a
few steps: backup ranger configs on znode, backup collections, delete Log
Search znodes, then upgrade `managed-schema` znode for Ranger.
--
To stop receiving notification emails like this one, please contact
[email protected].
