- Community Home
- >
- Software
- >
- HPE Ezmeral Software platform
- >
- Re: How to Re-Connect the Installer with the Clust...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2023 12:52 AM
08-08-2023 12:52 AM
How to Re-Connect the Installer with the Cluster
After failed incremental installation at the cluster, I abort the progress and the installer reset itself. After reset, Installer goes back to installation page. Now I need to re-connect the installer to the cluster.
Checked the files "/opt/mapr/installer/data/groups.json" and "/opt/mapr/installer/data/last_known_state.yaml" bot have old cluster information.
I tried to import the last know state (last_known_state.yaml) at Installer UI but not worked. What should I do for recover old cluster information?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2023 12:24 PM - edited 08-08-2023 12:26 PM
08-08-2023 12:24 PM - edited 08-08-2023 12:26 PM
Re: How to Re-Connect the Installer with the Cluster
Can you please explain a bit more about this issue?
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2023 02:34 AM - last edited on 08-09-2023 11:24 PM by Sunitha_Mod
08-09-2023 02:34 AM - last edited on 08-09-2023 11:24 PM by Sunitha_Mod
Re: How to Re-Connect the Installer with the Cluster
Well, let me start from scratch.
- I installed mapr installer using the mapr-setup script of Data Fabric to my one node named "mapr-installer"
- I installed data fabric using mapr-installer UI to 3 different nodes named "node-[1-3].example_domainname.com" with one ZK and CLDB. ZK and CLDB placed a node named "node-1.example_domainname.com"
- After the installation of the Data Fabric over 3 nodes, I used incremental installation to add more ZK to the cluster. So I select the other 2 nodes to install ZK too.
- Installation Failed (Here is the ticket about details of installation. But this issue is about Installer, the installation fail ticket is about ZK. So different cases happened at the same time)
- After fail happened at Installer, I selected Abort the installation to recover the old state (which is a clean installation with one ZK node)
- Abort action resets the Installer and now Installer not seeing the cluster already running. Now Installer is at the setup page and like there is no node installed Data Fabric. But Nodes are running services already.
- I tried to recover the Installer from "import state" option but not worked. As I mention above, I checked both "/opt/mapr/installer/data/groups.json" and "/opt/mapr/installer/data/last_known_state.yaml" files and both contains old successfully installed state of cluster.
I guess every step is clearly described. Please don't hesitate to ask questions because it may happen anytime and I want to know how to fix it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2023 03:35 AM
08-25-2023 03:35 AM
Re: How to Re-Connect the Installer with the Cluster
Installer DB can be regenerated using the 'Probe' and 'Import' Stanza commands as documented here:
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2023 11:38 PM - last edited on 09-01-2023 12:14 AM by Sunitha_Mod
08-30-2023 11:38 PM - last edited on 09-01-2023 12:14 AM by Sunitha_Mod
Re: How to Re-Connect the Installer with the Cluster
I guess here is the problem;
./mapr-installer-cli import -n -t /tmp/stanza.yaml
HPE Data Fabric Installer SDK
Logging in to localhost
Are you sure you want to import cluster (your current installer state will be lost)? [y/n]:y
Are you sure you want to reset config? [y/n]:y
Resetting the cluster...
Done
WARNING: You have configured your cluster with 2 data node(s). MapR does not support clusters with less than 5 data nodes in production outside MapR Edge. A data node is a node that runs the MapR FileServer process and is responsible for storing overall cluster data. Clusters with less than 5 data nodes will have a lower failure tolerance, and may not be able to sustain data integrity in the case of more than one failure. If this is a non-edge production cluster, please add more data nodes.
WARNING: You have configured your cluster with 1 cldb node(s). MapR does not recommend clusters with less than 3 cldb nodes in production. A cldb failure in a cluster with less than 3 cldb nodes can result in a cluster that is unaccessible or in read only mode. If this is a production cluster, please add more cldb nodes.
ERROR: import command failed
These hosts [node-2.treo.com.tr] must have 'mapr-core' in one of the 'groups' section of the template
Log files mapr-installer.log and installer_cli.log can be found at /opt/mapr/installer/logs
But in the community edition, CLDB and Zookeeper services are forbidden to install more than one node. How can we solve this issue? We should import the last known state to the installer even if the cluster has one node Zookeeper and CLDB installed.
Here are the installer logs: https://drive.google.com/file/d/1qYwJn3591bKNIPlRlW_Un9KFy7e7F3fx/view?usp=sharing