Bitbucket search log is massive

[networksystems.dhs@tn.gov]

Bitbucket search log is massive as 50 gb. It is crashing Bitbucket application and user cannot access the application. Is there way to shrink the size or make the log not to be that huge?

Thanks 

[Christian Glockner · Accepted solution]

Hi,

You can simply delete the file, or if you're running Linux, just run

echo 0>bitbucket-search.log

which will empty the file.

Cheers,

Christian

Premier Support Engineer

Atlassian

[Alex Hodge]

What's the way to configure this file so that similar outages can be avoided? i.e. a log file size rotate trigger.

I'm unable to find a setting in atlassian/application-data/bitbucket/shared/search/log42j.properties that achieves this. I have tried amending to get a SizeBasedTriggeringPolicy:

---

appender.rolling.type = RollingFile
appender.rolling.name = rolling
appender.rolling.fileName = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}.log
appender.rolling.layout.type = PatternLayout
appender.rolling.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker%.-10000m%n
appender.rolling.filePattern = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}-%d{yyyy-MM-dd}.log
appender.rolling.policies.type = Policies
appender.rolling.policies.time.type = TimeBasedTriggeringPolicy
appender.rolling.policies.time.interval = 1
appender.rolling.policies.time.modulate = true
appender.rolling.policies.size.type = SizeBasedTriggeringPolicy
appender.rolling.policies.size.size = 1GB

---

This doesn't seem to have an impact as it's for the rotated files, and not the base one.