Member since
07-12-2013
435
Posts
117
Kudos Received
82
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1656 | 11-02-2016 11:02 AM | |
2610 | 10-05-2016 01:58 PM | |
7252 | 09-07-2016 08:32 AM | |
7485 | 09-07-2016 08:27 AM | |
1695 | 08-23-2016 08:35 AM |
09-02-2015
07:25 AM
I believe that's because of replication. 2.21 TB refers to the amount of space taken up by the data you've stored plus the space taken up by all the replicas of that data. 1.88 TB refers to the amount of data you can store, accounting for the fact that HDFS will need space to make replicas.
... View more
08-28-2015
11:06 AM
7 Kudos
The Host Monitor is one of the "Management Services". From the main screen, you'll see all the CDH services in our cluster down the left-hand size, and below the cluster there is another box for the management services that are part of Cloudera Manager itself. You can probably fix it by just clicking on the drop-down arrow next to Management Services and click 'Restart'. If it continues, I'd click on Management Services, then drill down into 'Host Monitor' and look at the logs to see what errors are being given.
... View more
08-23-2015
07:00 PM
1 Kudo
No, VMware Fusion runs normal VMs, just like Player. I think you're thinking of Parallels? The QuickStart VM should work on Fusion - lots of users have done it. Anyway - I don't believe opening a disk is the right option - that's for when you want to install a new operating system in a blank VM using a .iso for (CD / DVD image). You're wanting to import or open an existing VM. It's the .vmx file you should be opening. I hope that helps - I don't have Fusion myself.
... View more
08-22-2015
07:30 PM
Do you get any error message? Is there any more detail you can provide like exactly what's shown on the screen and what steps you've taken? When you say VM Player, do you mean VMware? I would also suggest comparing the checksums to make sure your download isn't corrupted.
... View more
08-22-2015
07:27 PM
1 Kudo
I'm not seeing the specific error I'd expect in that log, but this could be because Intel VT-x / AMD-V extensions are not enabled. It's a BIOS setting - there have been several cases lately where the VMware image just didn't boot, and that was why.
... View more
08-14-2015
06:41 AM
I'd recommend you do the same - email support@gogrid.com using the email address you have on file, and they should be able to help you. With the GoGrid option, the underlying infrastructure is not controlled by Cloudera, so I'm afraid there isn't much we can do to help you without GoGrid's involvement if the initial deployment fails.
... View more
08-11-2015
08:03 AM
2 Kudos
>> First of all, can that be done? I haven't tried it, but I would expect problems. We recommend running the VM with Intel VT-x / AMD-V extensions enabled and I know there have been times when the VM won't start and it's because those extensions are not enabled. I don't believe these extensions are available to the guest operating system. >> Second, my VM player, VirtualBox, requires an *.iso file to install and start QuickStart from: is a *.iso file type included in the QuickStart VM download? The *.iso option is for when you're running a live disk image or installing an operating system on to a new virtual hard drive. The VM consists of an .ovf file (the metadata about the VM) and a .vmdk file (the virtual hard disk image). You should go to File -> Import Appliance... and open the .ovf file. >> Third, does QuickStart contain HBase, and does the QuickStart version have full functionality? The VM does contain HBase, and it is configured in 'distributed' mode, which means the Master and RegionServer are running in separate JVMs and using the same Zookeeper service as everything else - also in a separate JVM. However on a single node you're not going to have the parallelism or fault-tolerance of a cluster, obviously, so it is a very different environment to be working in. If you do want a full cluster or can't run the VM on hardware, you can try out Cloudera Live (cloudera.com/live) which gives you a full cluster in the cloud. HBase isn't started by default, but it's configured - just start the service in Cloudera Manager and you should be in business.
... View more
08-06-2015
09:31 AM
The Live-on-AWS deployment should cost about $25 - $30 per day, by my estimation based on the default instance sizes and the amount of EBS storage. Exactly how much it costs depends on exactly which options you choose during deployment, such as the region, instance sizes, whether you add the Tableau / Zoomdata applications, etc. It deploys 4 - 5 machines, however, so after 10 days you'll be running over the 750 hours.
... View more
08-06-2015
09:27 AM
As for the warnings in CM, most of them is CM warning you that you only have 1 node. Now, of course that's true because you're on a single VM, but Cloudera Manager will still warn you because that means you have no redundancy. But do keep this in mind - since this is all designed to be a distributed system, rebooting the VM is equivalent to resetting your entire datacenter - it'll take a minute for the services to all recover and be ready to service requests. With 8 GB of RAM most things should still work. We recommend having more if you can, but you will find that CM and the rest of the system will struggle if you start running larger jobs on the VM. The memory tuning in CM is significantly better in the 5.4 VM that should help prevent some issues, so you may consider trying the newer version if it continues to struggle.
... View more
08-06-2015
09:22 AM
I don't know why the services dies when you updated CentOS, I'd be curious to know what errors are in the various log files under /var/log if you simply updated CentOS packages. Restarting the machine is the easiest way to automatically restart everything in order, however in /etc/rc5.d, you can find symlinks created by the init system that are used to kill and start the services in order on shutdown and startup, respectively. if you look in that directory for symlinks starting with S, and ordered by the number following the S, you will see the complete list of services in order. But again, restarting the OS is easiest if you want to restart EVERYTHING, especially if it was some other service being updated that caused the failure in the first place. However, the bigger issue is going to be that you're no using Linux service management anymore. I see in the logs you ran this: sudo ./cloudera-manager --force The --force bypasses all the safety checks that you have enough resources. If you ran this before and continued to run with 4 GB of RAM, then that is why you've been unable to access services. However this script attempts to shutdown the existing CDH services through Linux service scripts gracefully, so you shouldn't have seen all the errors about the service being dead but the pid file existing. So now that you have launched Cloudera Manager, you should check the status of the service in Cloudera Manager's portal instead of using the service scripts. It will also take several minutes after a reboot before all services are running - Hue is among the last to be started by CM.
... View more