The action update, at its full capacity, is what the current build action does: user may want to change hdfs, hbase config values and use new image (compatible with the previous image).
One solution is to give action update the same capacity as action build - without the constraint of aforementioned check. Cheers On Fri, Jul 11, 2014 at 10:25 AM, Jon Maron <[email protected]> wrote: > Why would I want to leverage “build” to update the cluster rather than the > discussed “update” action? In both instances I don’t imagine the parameter > change should take place prior to a restart. Correct? > > — Jon > > On Jul 11, 2014, at 1:19 PM, Ted Yu <[email protected]> wrote: > > > Hi, > > When I issue action build on an existing cluster, I get: > > > > 2014-07-11 17:15:05,377 [main] ERROR main.ServiceLauncher - Application > > Instance dir already exists: hdfs:// > > hor10n03.gq1.ygridcore.net:8020/user/yarn/.slider/cluster/cl1 > > 2014-07-11 17:15:05,378 [main] INFO util.ExitUtil - Exiting with status > 75 > > > > I want to get opinion on relaxing the above check. > > I think user should be allowed to change parameters for an existing > cluster. > > > > Cheers > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
