Member since
01-09-2014
283
Posts
70
Kudos Received
50
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1698 | 06-19-2019 07:50 AM | |
2723 | 05-01-2019 08:07 AM | |
2772 | 04-10-2019 08:49 AM | |
2667 | 03-20-2019 09:30 AM | |
2357 | 01-23-2019 10:58 AM |
06-20-2017
09:58 AM
Hi @pdvorak, thanks a lot for you answer, I've already checked that page and it helped. Thanks again. DB
... View more
06-05-2017
09:21 AM
You could have an issue with certificates...if you enable DEBUG for the client, you should be able to determine what it's having issues with: cp /etc/kafka/conf/tools-log4j.properties /var/tmp sed -i -e 's/INFO/DEBUG/g' /var/tmp/tools-log4j.properties export KAFKA_OPTS="-Dlog4j.configuration=file:/var/tmp/tools-log4j.properties -Djava.security.auth.login.config=/path/to/jaas.conf" -pd
... View more
04-21-2017
06:13 AM
That is a fair question of what is 'appropriate'. I was hoping there would be an option to select a default behavior to do so. For example, upon 'usr1' creating an index, the following permission would be generated: collection='the_new_idx"->user=usr1->action=* I imagine other global default behaviors could exist such that the auto-generated permission sets access for new collections at a role level instead of user level.
... View more
03-27-2017
12:11 PM
1 Kudo
meta.properties was likely left over from a previous instance of the kafka broker. Did you remove the broker role instances and recreate them on the same machine? When that happens, the broker.id changes and kafka won't start properly as a safety measure. A good rule of thumb is if you need to remove the role instances and recreate, then delete everything from the kafka data dir (unless you need to use the partitions), in which case, you'll have to update that meta.properties file manually. -pd
... View more
03-22-2017
03:00 PM
Mathieu is correct, you can use: solrctl instancedir --update collection1 /path/to/collection1 solrctl collection --reload collection -pd
... View more
03-14-2017
04:49 AM
Spot on, I missed the directory structure and just dumped my jars under plugins.d. The cmd line did not give me clues since it did not have anything related to plugin directories, e.g. "--plugins-path /usr/lib/flume-ng/plugins.d:/var/lib/flume-ng/plugins.d". Thanks!
... View more
03-07-2017
12:51 AM
The above link shows the issue as still open with Unresolved status. Is this bug resolved? I am using Cloudera 5.9, Hue 3.10 & Solr 4.10.3. I am also facing the same issue. Please let me know how to resolve this.
... View more
01-06-2017
03:49 PM
Hi @pdvorak, Thanks for your comments. The answer to all three questions are Yes. My iptables is turned off. I can ping my NN and tranverse hdfs. The problem was, the IP for hdfs sink I gave was private IP and once I changed it to public. It started streaming the data. So, the issue is resolved. 🙂
... View more