About sphinxid

alvarolucas · ‎11-09-2017

Hi, as usual, it depends of what you need... The cloudera VM has 1 node with everything and it allows you to see it... A quite simple cluster could have 2..3 MVs for CM & masters and at least 3 VMs for Workers. As I said and as you can imagine, it depends what you want to test on it Believe me, you really need a Cloudera admin to get what you want... In another thread refered to this blog I hope, this will help you

NaveenGangam · ‎10-06-2016

Awesome !! Thanks for the update.

Harsh J · ‎07-22-2015

A direct property to change this is now available in the most recent CM 5.4.x releases. Once you upgrade, please remember to remove the env-var workaround so things continue to be configured consistently.

sphinxid · ‎05-21-2015

Now the cluster that previously didn't see cdh 5.4.1 parcels got 5.4.2-1.cdh5.4.2.p0.2 parcel update available. I believe this is probably the cause. (cloudera defer the 5.4.1 and waited for the 5.4.2 being pushed instead, because the release time is quite close) Look: http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cdh_rn_new_in_542.html

sphinxid · ‎12-19-2014

ok i found out the problem. I use CDH 5.2.1. In my case, it happened when I use YARN to manage Impala resources. (default config) Then those error msg appeared.

Online	Offline
Last Visited	‎11-15-2016 09:27 PM

Member Since	‎12-18-2014 11:37 PM
Last Visited	‎11-15-2016 09:27 PM
Posts	19
Kudos received	1

Cloudera Community

Re: Problem when upgrading to CDH 5.4.1 (Parcels -

Re: Problem in YARN (distcp) - sometime gives erro...

Re: Minimum number of nodes, and specs for a real ...

Re: (5.8.2-1.cdh5.8.2.p0.3) Hive on Spark "Complet...

Re: How do you change Kafka heap memory with CDH (...

Re: Problem when upgrading to CDH 5.4.1 (Parcels -

Re: Problem in YARN (distcp) - sometime gives erro...