That particular -D properties is not currently accepted by Oozie. You¹d have to manually delete the .oozie-auth-token file from your submission dir and try again with your new principal.
‹ Mona On 3/24/14, 2:40 AM, "Adrian Liu" <[email protected]> wrote: >Hi all, > >I¹m working on a secured hadoop cluster. I used to work using kerberos >principal, then I want to switch to use another principal. But it seemed >that oozie cached the previous ticket so it showed that my job was >submitted by the previous principal >. I tried to set -Doozie.auth.token.cache to be false like bellow but it >doesn¹t work. > > >oozie -Doozie.auth.token.cache=false job -run config MY_CONFIG auth >KERBEROS > > >Could you please help on that? Thanks. > >Adrian >
