I have installed a HDP 2.2.4.2 cluster with 2 nodes both having CentOS 6.6 OS. I need to add one more host to this cluster but i didnt find any option to do this on the the ambari console (ambari version is 2.0) . Is there any way I can add more hosts to this cluster?
It really depends on the version of Ambari you have. For Ambari 1.7.0, 2.1.0 and 2.1.1:
Go to the 'Hosts' tab. In the top left corner you will see an 'Actions' drop down button; within that drop down menu you will see 'Add New Hosts'.
I don't have a 2.0.0 environment to test on but I would imagine if versions prior to 2.0.0 and after have it in the same spot, it would also be located in the same place.
You can also add hosts using the REST API. Details can be found on the Ambari Wiki
On the top right corner there is an admin drop down button where you inspect your current nodes and add more as well.
You can find it under hosts tabs. Screenshot will make it more clear
Related
I've successfully installed Ambari server/agent 2.7.5 on my Centos 7 machine. Now i am facing an issue while installing a cluster in the install wizard at the "Select version" step. I have no versions showing in my dropdown. What can be the issue?
ps: see screenshots
my content in /var/lib/ambari-server/resources/stacks/HDP
install wizard screenshot
Now that ambari has come back to life, this conversation is relevant despite other stack members feels. Additionally 100s if not 1000s of companies are still using free open source ambari w/ free open source HDP.
When you are building ambari 2.7.5 from source, you need to feed it a stack. HDP was one of them, that is no NLA unless you copied it.
The last free HDP repos you need are found here:
https://www.makeopensourcegreatagain.com/rpms/
And you can find instructions about how to use these here:
https://github.com/steven-matison/dfhz_ddp_mpack
Step 1:
Copy HDP 3.0 and 3.1 Stack to /var/lib/ambari-server/resources/stacks/hdp, and then restart ambari-server
Step 2:
After clicking the "Add Version" button，for details, please refer to https://www.yuque.com/create17/mxswdh/pqrb9q#tsdHa
For the premise, you need to have an HDP-related RPM package.
It appears that my kibana installation did not contain the grokdebugger plugin since I was not able to find it in /usr/local/www/kibana6/ and it did not appear under the Dev Tools pane.
I did install it by installing x-pack using elasticsearch-plugin and kibana-plugin. This required removing a few of these x-pack plugins after installation since they were reported as being red status upon visiting the Kibana page. However, I successfully removed them and Kibana loads as normal; but there is no grokdebugger. The grokdebugger source directory is present in /usr/local/www/kibana6/plugins/x-pack/plugins/, and its contents appear to be normal, but it does not appear in the Dev Tools section.
I would rather consult some experts before diving too much deeper and messing things up (more than I already have).
It is worth mentioning, this is a new installation so I am open to deleting anything or installing anything from scratch if that is cleaner or easiest.
Thanks~
Edit
I've noticed that only a few of the plugins that are in src/core_plugins are loaded, according to the logs:
elasticsearch
kibana
timelion
metrics
console
There are numerous other plugins in that directory which are not being loaded. I tried placing grokdebugger in there from where it was in plugins/x-pack, but it also was not picked up.
We do not get an issue if we install SQ5.6 on a client machine but on our Amazon servers when we fire up the server for the first time with defaults so we can install plugins, we get:
Note the black, empty menu at the top of the screen. We get this in chrome and IE11. Previous versions of SQ did not have this issue.
We have the pre-requisites correctly installed, so any ideas what could be causing this?
Thanks in advance.
Upgrade to latest (Version 5.6) using yum.
http://localhost:9000/setup
Fixed!
It does help if the browser being used is actually listed as compatible on the SonarQube site :D
http://docs.sonarqube.org/display/SONAR/Requirements
I have puppet 3.4.2 and Vagrant 1.6.5. We configured our puphpet setup over a year ago.
This is all working fine on my environment, but a fresh install downloads a new version of the base box which has an updated version of puppet and so our old configurations don't work.
We are using this box: https://atlas.hashicorp.com/puphpet/boxes/ubuntu1204-x64. I must have v1 but for new instances it will download v2.1
I have tried updating the puphpet config.yaml, but when I upload this to puphpet.com I get the message "The config file provided was empty! Please recreate your manifest manually below.".
So I see a few solutions but I have blockers on each of them:
Use the old base box. Is there an archive copy of V1 of this server somewhere on the internet? https://atlas.hashicorp.com/puphpet/boxes/ubuntu1204-x64
Use the new base box but downgrade Puppet. How do you downgrade Puppet and all it's dependancies?
Figure out some way of importing my config.yaml in to puphpet.com and start using the new versions. Is there anything I need to do to get puphpet.com to recognise an old file?
Reconfigure the whole file from scratch. Do you know anyone that can help me?
Thanks for advice.
It's still there, but no longer supported or publically listed.
All boxes come pre-installed with Puppet 3.4.3, which is BC with 3.4.2.
Sorry, changes in the past month or two have broken BC with old config.yaml files. You'll need to manually select your options again.
Just do this. Honestly, it's textboxes, dropdowns and radio boxes, and will take you less than 10 minutes.
Please help!
I have an installation of magento v 1.5.1 and I want to upgrade it to 1.7 but when i try to
list upgrades, this is what i only see:
wp_theme_grayscale: 1.0.7 => 1.4.0
RicoNeitzel_VertNav: 0.3.1 => 0.4.0
Locale_Mage_community_fr_FR: 1.7.0.0 => 1.7.0.1
TBT_Enhancedgrid: 1.3.2.1 => 1.031
any suggestions?
after upgrading all,
and tried to list all upgrades again,
it couldn't see any upgrade anymore.
your help would be much appreciated.
EDIT:
I used this guide. http://turnkeye.com/blog/magento-upgrade-guide/
I did not get any error. the updates above are just the updates that i can see,
OK, I can share my successful experience of upgrading:
Go to System -> Magento Connect -> Magento Connect Manager
Log in using your username and password
Click on “Check for Upgrades” button
4.You will notice that most package rows turn to yellow. These packages are the only that have available updates. Go to each package row, click on “Actions” drop-down menu and select the most current stable version available.
Note: Stable version available may vary for each package. For example, some packages may have 1.7.0.2 upgrade version and others 1.7.0.1 or lower. Don’t bother with this, just pick the latest stable version available.
When you are done selecting upgrade version for all packages, click on “Commit Changes” button.
Now, you have to wait. Give it some time. During upgrading process, you may see various notes or outputs that may be tricky and you may think that the process is done. Well, IT IS NOT. Just wait, give it some more minutes. The process will be done when there is no activity in the “command line” like console for about one minute.
Click on “Refresh” button. You are almost done! Technically, you have completed the upgrade process.
Go to your cPanel file manager or your FTP client and delete EVERYTHING in var/ directory.
Last but not least, reindex data in Admin -> Index Management
When you enter admin section and scroll down, you will notice that it says “Magento ver. 1.7.0.2”
This process worked for me fine.
Please try to run
./mage list-upgrades
In some cases there might be no Mage_* entries in the list. In this case the following command can be used:
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force
I got it working now.
what i did is after the upgrade, i re uploaded my database back up, and viola the error is gone. The error has a hint, and yes because of duplicate thing that it could not continue if the table already exist.