Hey Markovich,   Within CM, there are several tunible properties for all the various modules that are not common enough to have options in CM.  To handle those options, you can add them as a safety valve.  To do this:   - Go to Services->MapReduce->Configuration(View and Edit). - Then expand Service-Wide and click on Advanced.  - There you should see "MapReduce Service Configuration Safety Valve for mapred-site.xml".  Paste the following in there based on the value you want to set for the number of cache directories:   <property>    <name>mapreduce.tasktracker.local.cache.numberdirectories</name>    <value>5000</value> </property>   - Then save the config and restart the Mapreduce service.   This is true for all the various modules.  If you don't find the value when you search, it's probably not settable, but every module will have an Advanced with a "Safety Valve", so you can put your properties in there when necessary.   Hope this helps.   Thanks Chris   ... View more

Hey Markovich,   Are you running the workflow from inside Hue or from the Oozie command line?  If from within Hue, then you are running into HUE-1631 and it won't be fixed until a later release of CDH.  If you are not using Hue, can you attach your job.properties file and workflow?   Thanks Chris ... View more

Hey Srini,   When you first created the collection, you ran a command similar to:   - solrctl instancedir --generate $HOME/solr_configs   This command was what created the configs that you imported for solr.  You can see the various configs by running:   - solrctl instancedir --list   Then pick the config that goes with your collection and run:   - solrctl instancedir --get <name_from_list> /path/to/local_fs   Then change the schema.xml in /path/to/local_fs/conf and run:   - solrctl instancedir --update <name_from_list> /path/to/local_fs   Then the schema will get updated.  Note, when you update the schema, you have to reindex all your documents or else they won't have indexes for the latest schema changes.   Hope this helps.   Thanks Chris ... View more

Hello,   You have two options here:   - As dvohra mentioned, you could copy the morphline.conf file to /etc/flume-ng/conf and then give a full path in your agent config in CM.  Then restart. - If you are wanting to use the "Flume-NG Solr Sink" config section in CM to config your morphlines, then you need to change "morphline.conf" to "morphlines.com", notice the "s" at the end.  Here is my agent config as an example:   avro.sources=src avro.sinks=solrSink avro.channels=memoryChannel avro.sources.src.type=avro avro.sources.src.bind=cdh43-1.test.com avro.sources.src.port=8889 avro.sinks.solrSink.type=org.apache.flume.sink.solr.morphline.MorphlineSolrSink avro.sinks.solrSink.channel=memoryChannel avro.sinks.solrSink.morphlineFile=morphlines.conf avro.channels.memoryChannel.type=memory avro.channels.memoryChannel.capacity=4096 avro.channels.memoryChannel.transactionCapacity=100 avro.channels.memoryChannel.byteCapacity=0 avro.sources.src.channels=memoryChannel   You can also see the morphlines file that CM is trying to use by looking in "/var/run/cloudera-scm-agent/process/<id>-flume-AGENT" where <id> is the most recently created.  You'll see a "morphlines.conf".   Hope this helps...   Thanks Chris   ... View more