[
https://issues.apache.org/jira/browse/RANGER-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759434#comment-17759434
]
Bhavik Patel commented on RANGER-4357:
--------------------------------------
[~fateh288] thanks for reporting this.
Have you also validated for default .json format?
On my cluster Im observing file rollover is not effective for
hbaseRegion(specifically) server, are you also observing the same?
{code:java}
orc.buffersize=10mb
orc.stripesize=10mb
filespool.buffer.size=10k
file.rollover.sec=1day
xasecure.audit.provider.queue.size=1mb default {code}
With the above configuration Im observing logs are accumulating in the
filespool directory. Do I need to optimise any config?
> Enabling ORC audit for hdfs destination should not require 2 separate
> configurations
> ------------------------------------------------------------------------------------
>
> Key: RANGER-4357
> URL: https://issues.apache.org/jira/browse/RANGER-4357
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Fateh Singh
> Assignee: Fateh Singh
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently there are 2 configs which will be required to enable orc i.e.
> xasecure.audit.destination.hdfs.batch.filequeue.filetype=orc and config
> xasecure.audit.destination.hdfs.filetype=orc
> Ideally, we would want only 1 config to enable orc
> xasecure.audit.destination.hdfs.batch.filequeue.filetype=orc. Also, orc can
> only be enabled from filequeue, so above config seems more reasonable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
