bq. introduce a special config flag to disable the Cancel functionality +1
Similar config is used in other project(s) such as hbase. On Fri, Aug 25, 2017 at 2:54 PM, Robert Metzger <rmetz...@apache.org> wrote: > Hi Raja, > > you can actually disable the UI by setting the port to a negative number. > The configuration property is "jobmanager.web.port". > I'm not sure how well this is tested, but from the code it seems that this > is the behavior of Flink. > > If that doesn't work, I would propose to add a change to Flink to > introduce a special config flag to disable the Cancel functionality in the > UI. > The change is probably not too hard to do. > > Regards, > Robert > > > > On Thu, Aug 24, 2017 at 7:04 PM, Raja.Aravapalli < > raja.aravapa...@target.com> wrote: > >> >> >> Hi, >> >> >> >> I have started a Flink session/cluster on a existing Hadoop Yarn Cluster >> using Flink Yarn-Session, and submitting Flink streaming jobs to it… and >> everything works fine. >> >> >> >> But, one problem I see with this approach is: >> >> >> >> The Flink Yarn-Session is running with a yarn application id. And this >> application id is visible in Yarn Resource Manager UI. >> >> >> >> And this flink-session can be tracked from resource manager to Flink >> Session UI >> >> >> >> From which other users on the Hadoop cluster was able to see and *CANCEL* the >> running Flink jobs! >> >> >> >> Users who are browsing the UI are un-expectedly hitting the button >> without knowing the impact…. !! Can someone pls guide me on how to control >> this in UI ? >> >> >> >> >> >> Thanks a lot. >> >> >> >> Regards, >> >> Raja. >> > >
