Thanks for the suggestions, Matt. That's a good point about the hostname resolution happening before the proxy connection. I haven't tried adding the hostname to the hosts file yet, so I'll test that next. I'll also compare the ping and nslookup results on both the NiFi 1.26.0 and 2.7.2 servers to see if there's any difference in DNS resolution. If the hostname resolves correctly but the issue still occurs only in 2.7.2, it may point to a regression in the newer version's handling of proxy or DNS resolution. I'll update the thread once I have the results. Thanks again! ... View more

The behavior you are seeing is due to Impala’s Clamp MEM_LIMIT query option combined with how you specified the memory limit value. Here is exactly what is happening and how to fix it: 1. Why it is clamping to 2GiB When you set the limit to 10000000 without a suffix, Impala interprets that value strictly in bytes, which equals ~10 MB. Because 10 MB falls far below your configured pool floor (min-query-mem-limit.root.default of 2GiB), the Admission Controller automatically forces ("clamps") the query limit up to your 2GiB minimum. For a heavy query, 2GiB isn't enough, resulting in the OOM error. 2. Why the memory estimate changes when you manually set MEM_LIMIT When you explicitly define a MEM_LIMIT (like 4G or 8G), Impala’sNormally I can help with things like this, but I don't seem to have access to that content. You can try again or ask me for something else. ... View more