Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/14659
This context is just something passed over IPC to provide a general string
for the audit logs, the main actual access of it is in the HDFS audit log
```
HdfsAuditLogger hdfsLogger = (HdfsAuditLogger) logger;
hdfsLogger.logAuditEvent(succeeded, ugiStr, addr, cmd, src, dst,
status, CallerContext.getCurrent(), ugi, dtSecretManager);
```
Otherwise it gets passed along RPC calls (along with htrace context), and
set by the various entry points (CLI, MR, etc). Lets you find out which piece
of code is bringing your NN to its knees. See
[HDFS-9184](https://issues.apache.org/jira/browse/HDFS-9184)
I'd nominate @cnauroth as someone capable of reviewing the link up with
HDFS; he's happy now that there aren't spaces in the context string.
Spark-wise: I've added a comment on how a test for this could be written.
The HBase keytab reflection code showed me how brittle some of that stuff can
be to changes in the reflected-on classes
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
