On 2/27/2013 9:48 AM, Eric Newton wrote:
Sure, just create a ticket and submit a patch, if you're up to it.
I'm not afraid of contributing here. I do elsewhere. Unfortunately, a patch + custom build for our project is not allowed. The effort requires unpatched 1.4.2, so I figured I'd ask. It looks like (after browsing the source a bit), I will have to figure out a workaround. If I'm feeling saucy and can make sense of it, I will try to follow up with a patch some day so that this is addressed for the next person. I'm not a Java developer, but do comprehend most of the basic code I've seen in the repo based on previous Java reading.
On Wed, Feb 27, 2013 at 9:38 AM, Jeff Blaine <[email protected] <mailto:[email protected]>> wrote: We spin up our slaves first, then the Hadoop namenode + Accumulo master afterward. By the time that comes up, tserver has exited on the Accumulo slaves. Is there a way to increase the tserver effort for connection to the master? Aside: is there really any reason for tserver to exit? Why not just do an exponential backoff of connection attempts until 30 seconds is hit, and then stay there infinitely?
