There’s no way to do that. Once YARN launches containers, it doesn’t communicate with them for anything after that. The tasks / containers can obviously always reach out to YARN services. But even that in this case is not helpful because YARN never exposes through APIs what it is doing with the tokens or when it is renewing them.
What is it that you are doing? What new information are you trying to share with the tasks? What framework is this? A custom YARN app or MapReduce / Tez / Spark / Flink etc..? Thanks +Vinod > On Oct 7, 2022, at 10:40 PM, Julien Phalip <jpha...@gmail.com> wrote: > > Hi, > > IIUC, when a distributed job is started, Yarn first obtains a delegation > token from the target resource, then securely pushes the delegation token to > the individual tasks. If the job lasts longer than a given period of time, > then Yarn renews the delegation token (or more precisely, extends its > lifetime), therefore allowing the tasks to continue using the delegation > token. This is based on the assumption that the delegation token itself is > static and doesn't change (only its lifetime can be extended on the target > resource's server). > > I'm building a custom service where I'd like to share new information with > the tasks once the delegation token has been renewed. Is there a way to let > Yarn push new information to the running tasks right after renewing the token? > > Thanks, > > Julien
