Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 10-21-2014 07:35 PM - edited 09-16-2022 02:10 AM
Hi,
I tried to set mapreduce.shuffle.max.connections to 0, but a validation error occured.
The doc says:
Set to 0 (zero) to indicate no limit on the number of connections.
Error: 0 is less than the minimum allowed value 1.
Please see the attached screenshot.
Version: Cloudera Enterprise Data Hub Edition Trial 5.2.0 (#60 built by jenkins on 20141012-2239 git: 179000584849e68f98ad2a7fe710723bd6c29c98)
CDH: 5.1.2
Regards,
Created 05-29-2015 10:43 AM
Hi Jiro,
Thanks for bringing this to our attention. It appears there's a bug with the validation for that property, in which the lower bound should be 0 and not 1. We'll get this fixed in a future release. In the meantime, you can accomplish setting mapreduce.shuffle.max.connections to 0 by setting it in a specific Safety Valve in Cloudera Manager. Please follow the directions listed below:
<property> <name>mapreduce.shuffle.max.connections</name> <value>0</value> </property>5. Save changes then Deploy client configuration
Kind Regards,
Anthony
Created 05-29-2015 10:43 AM
Hi Jiro,
Thanks for bringing this to our attention. It appears there's a bug with the validation for that property, in which the lower bound should be 0 and not 1. We'll get this fixed in a future release. In the meantime, you can accomplish setting mapreduce.shuffle.max.connections to 0 by setting it in a specific Safety Valve in Cloudera Manager. Please follow the directions listed below:
<property> <name>mapreduce.shuffle.max.connections</name> <value>0</value> </property>5. Save changes then Deploy client configuration
Kind Regards,
Anthony
Created 05-29-2015 10:21 PM