About silvio_delval

silvio_delval · ‎05-11-2017

Great!! Well, I was thinkg about installing these v0.10 brokers in other empty machines. I suppose it's imposible to manage these v0.10 brokers in same Ambari, right? Maybe I should have both HDP versions installed, but only one of them is current...well, to difficult maybe. Anyway, thank you very very much for your answers, you saved my life 🙂 I'll mark your answer as accepted 🙂

silvio_delval · ‎05-11-2017

So, do I have to chroot existing cluster too? This 4 brokers group is in production and I can´t stop them. Apart from this, I'll install 3 new brokers in a second cluster but this will be v0.10. Can I use same zookeepers? I have HDP-2.3.2-2950 and I'll install this second group from HDP-2.6 repositories

silvio_delval · ‎05-10-2017

I enter ZkCli but I don't know how to do

silvio_delval · ‎05-10-2017

Well, we have currently running 4 v0.8 brokers with default config. How should I config Zookeepers to specify new brokers in second cluster?

silvio_delval · ‎05-10-2017

Well, we have currently running 4 v0.8 brokers with default config. How should I config Zookeepers to specify new brokers in second cluster?

silvio_delval · ‎05-10-2017

Hello, We are currently running 4 kafka brokers v0.8 in our cluster (HDP-2.3.2-2950) and we would like to test some v0.10 brokers in the same cluster. Is this possible? I was thinking about installing manuallly in some machines of the cluster from HDP-2.6.0 repo and apart from Ambari, but I don't know how this will affect zookeepers and if the whole of brokers will be seen as 2 groups of brokers and will work indepently. I would need advice 🙂 Regards, Silvio

silvio_delval · ‎02-23-2017

Well, I tried to debug some days ago but I didn't understand why it was stopping 20 seconds in a single point after the command. In nodes when the query is slow, it always stops here: 17/02/23 12:28:50 DEBUG ipc.Client: getting client out of cache: org.apache.hadoop.ipc.Client@1a942c18 17/02/23 12:29:10 DEBUG unix.DomainSocketWatcher: org.apache.hadoop.net.unix.DomainSocketWatcher$2@173ba36d: starting with interruptCheckPeriodMs = 60000 It seems to take 20 seconds (and always 20 seconds) to get the client out of cache, while in namenodes it takes no time, that's why queries are faster....but I don't know what "get the client out of cache" means....

silvio_delval · ‎02-22-2017

Hi Ana, Thanks for your answer. Well, all cluster machines are connected to the same physical switches, so I don't think it's a network problem. I think it has to be something regarding configs...but I don't know.

silvio_delval · ‎02-20-2017

Hi, I tried to find answers in previous posts, but I didn't find them. Well, I have very slow responses from commands like "hdfs dfs -ls /" executed in cluster members other than namenodes. Comparing responses, a simple "hdfs dfs -ls /" in a namenode lasts from 2 to 3 seconds, while in any other cluster computer this time is 22 seconds. I tried to debug the process but I can´t find anything different among them. When answer is slow, it always stops for 20 seconds after "DEBUG ipc.Client: getting client out of cache: org.apache.hadoop.ipc.Client@3c77d488" and before "DEBUG unix.DomainSocketWatcher: org.apache.hadoop.net.unix.DomainSocketWatcher$2@130263db: starting with interruptCheckPeriodMs = 60000". Any help? Best regards, Silvio

silvio_delval · ‎12-19-2016

Ok, thank you very much for answering 🙂

Online	Offline
Last Visited	‎06-12-2017 03:50 PM

Member Since	‎06-14-2016 09:59 AM
Last Visited	‎06-12-2017 03:50 PM
Posts	38
Kudos received	4

Cloudera Community

Re: Run multiple broker versions in the same clust...

Re: Run multiple broker versions in the same clust...

Re: Run multiple broker versions in the same clust...

Re: Run multiple broker versions in the same clust...

Re: Run multiple broker versions in the same clust...

Run multiple broker versions in the same cluster

Re: Very slow hdfs command responses in cluster me...

Re: Very slow hdfs command responses in cluster me...

Very slow hdfs command responses in cluster member...

Re: What the commands "enable_table_replication" o...