* #62 - Added a Force copy flag in case the hadoop cluster is version 2*...


* #62 - Adding an optional -f flag to hadoop copy commands in case of hadoop2 clusters.
* #67 - Added retries while updating the job to status running after successful launch.
* Changed scripts to create a sample cluster with version 2.4.0.
Considering this is synchronous call (submit job) wouldn't exponential back-offs increase latency too much? My theory is that the exception at this point is generated only when the threads give up and deadlock is resolved, so a retry should help. Thoughts?