About alexmc6

alexmc6 · ‎11-28-2018

Tim Armstrong wrote: Also, a more general tip is that you can set a default value for *any* query option via the dynamic resource pool interface. That is really helpful. Thanks!

alexmc6 · ‎11-28-2018

Sorry Tim. Setting max limits in resource pools is not an option for us. They are based upon the estimated memory consumption and the estimates are sometimes wildly innacurate. This has resulted in valid production queries being blocked from running.

alexmc6 · ‎11-27-2018

EricL: Can we do the equivalent of "SET MEM_LIMIT=100g;" in cluster wide config? ie can we enforce this so that no Impala query will suck up all the memory on the Impala service?

alexmc6 · ‎08-29-2018

Thanks for the information!

alexmc6 · ‎08-08-2018

But with Informatica BDM you also have Blaze and Spark as alternative engines to Hive. The original post was quite vague and may not have been BDM related at all.

alexmc6 · ‎08-08-2018

" UTC timezone conversion issue going on with only Parquet backed tables." > how do Cloudera Customers deal with this issue? I fear the first solution is to have all your servers use the same (UTC) timezone. We also have this flag setconvert_legacy_hive_parquet_utc_timestamps=true and hope to get rid of it once we move everything to UTC.

alexmc6 · ‎08-01-2018

Hello bgooley, Thanks for your suggestion. I am re-reading the docs and I still think it tells me to add a CM peer any time I want to do a BDR replication, but I can accept that maybe my reading of the docs is wrong. I have been re-trying my tests without a peered CM but was not able to improve the situation. In the meantime we have taken a different track and started to use a new cluster as the target with a new Cloudera Manager and BDR seems to be working for that.

alexmc6 · ‎08-01-2018

Hello Jim, That seems to have been the problem. Although the krb5.conf files were effectively identical the two Cloudera Managers had been configured by specifying the KDC by name and by IP address. We now have BDR working between two different Cloudera Managers, but not between two clusters with the same Cloudera Manager.

alexmc6 · ‎07-24-2018

has anyone seen this error when trying to set up Cloudera Manager backup BDR peering between two Kerberized clusters? (I think they are both 5.13.3) Source and target realms are same but have different KDC. Please ensure those KDCs are on unified realm. As far as I can see I am using the same KDC on both clusters. Can anyone suggest how I can check? I have looked in the /etc/krb5.conf They seem the same. I have done an nslookup on what it says is the KDC server - it is the same. Any more tips for things to look for?

alexmc6 · ‎07-23-2018

> you are replicating from one Hive Service to another on the same cluster. No,, not the same cluster. Two different (but similarly named) clusters, one Cloudera Manager.

Online	Offline
Last Visited	‎11-29-2018 08:22 AM

Member Since	‎02-19-2018 09:28 AM
Last Visited	‎11-29-2018 08:22 AM
Posts	29

Cloudera Community

Re: Impala - Memory limit exceeded

Re: Impala - Memory limit exceeded

Re: Impala - Memory limit exceeded

Re: Why/How is hive replication through BDR "singl...

Re: How to connect Impala/Hive with Informatica

Re: How in Hive to write to a timestamp in a parqu...

Re: Why/How is hive replication through BDR "singl...

Re: Weird BDR error saying different KDC

Weird BDR error saying different KDC

Re: Why/How is hive replication through BDR "singl...