My bad... Notice that setting it to 0 overrides the value to Integer.MAX_VALUE. So setting it to 0 is equivalent to Integer.MAX_VALUE (the default). So the documentation that default is 0 ... is fine.
From: Roshan Naik <[email protected]<mailto:[email protected]>> Date: Tuesday, March 24, 2015 2:54 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: hdfs.retryInterval - issues Sorry for typo.... I meant to say 'hdfs.closeTries' and not 'hdfs.retryInterval' -roshan From: Roshan Naik <[email protected]<mailto:[email protected]>> Date: Tuesday, March 24, 2015 2:52 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: hdfs.retryInterval - issues hdfs.retryInterval seems to have a some issues. * The default is not 0 as documented. * This statement does not seem to reflect the implementation: "If set to 0, the sink will try to close the file until the file is eventually closed". Setting it to 0 seems to be same as setting it to 1 .. AFAICT. * Seems like no way to indicate unlimited tries.
