Thanks @Takanobu for your reply. I will make it configurable and default as
disable.
Takanobu Asanuma 于2021年10月13日周三 下午3:34写道:
> I think many users parse audit logs in their own way, and they will be
> affected if the format is changed. So I agree with Masatake's suggestion.
> - Takanobu
>
>
I think many users parse audit logs in their own way, and they will be
affected if the format is changed. So I agree with Masatake's suggestion.
- Takanobu
2021年10月11日(月) 18:19 tom lee :
> Thanks @Masatake Iwasaki for your
> suggestion. This is a good idea.
>
> Masatake Iwasaki 于2021年10月11日周一
Thanks @Masatake Iwasaki for your
suggestion. This is a good idea.
Masatake Iwasaki 于2021年10月11日周一 下午3:26写道:
> > I am not sure whether we can directly go and change this. Any changes to
> Audit Log format are considered incompatible.
> >
> >
>
I am not sure whether we can directly go and change this. Any changes to Audit
Log format are considered incompatible.
https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Compatibility.html#Audit_Log_Output
Adding a field for caller context seemed to be accepted since it
However, adding port is to modify the internal content of the IP field,
which has little impact on the overall layout.
In our cluster, we parse the audit log through Vector and send the data to
Kafka, which is unaffected.
tom lee 于2021年10月11日周一 下午2:44写道:
> Thank Ayush for reminding me. I also
Thank Ayush for reminding me. I also have similar concerns, so I published
this discussion, hoping to let the members of the community know about this
matter and then give suggestions.
Ayush Saxena 于2021年10月11日周一 下午2:38写道:
> Hey
> I am not sure whether we can directly go and change this. Any
Hi all,
In our production environment, we occasionally encounter a problem where a
user submits an abnormal computation task, causing a sudden flood of
requests, which causes the queueTime and processingTime of the Namenode to
rise very high, causing a large backlog of tasks.
We usually locate