-
Bug
-
Resolution: Fixed
-
Major
-
None
The CPU usage is peaking when filtering is enabled.
[com.cloudbees.jenkins.support.filter.ContentFilters plugin="support-core@2.50"] [enabled]true[/enabled] [/com.cloudbees.jenkins.support.filter.ContentFilters]
The logs are displaying stacktraces related to this anonymization
at java.util.regex.Pattern$Start.match(Pattern.java:3463) at java.util.regex.Matcher.search(Matcher.java:1248) at java.util.regex.Matcher.find(Matcher.java:637) at java.util.regex.Matcher.replaceAll(Matcher.java:951) at com.cloudbees.jenkins.support.filter.ContentMapping.filter(ContentMapping.java:96) at com.cloudbees.jenkins.support.filter.SensitiveContentFilter.filter(SensitiveContentFilter.java:56) at com.cloudbees.jenkins.support.filter.AllContentFilters.filter(AllContentFilters.java:43) at com.cloudbees.jenkins.support.filter.FilteredOutputStream.filterFlushLines(FilteredOutputStream.java:185) at com.cloudbees.jenkins.support.filter.FilteredOutputStream.write(FilteredOutputStream.java:125)
Workaround
Disable the bundles anonymisation from the global settings
- is related to
-
JENKINS-21670 Option to anonymize customer labels
-
- Closed
-
- links to
After analysing the issue I've seen that the CPU usage is high even in support-core-2.47, which is the version previous to anonymization since it's moving huge files.
Anonymization implies the process of huge files such as logs. The difference is the process time needed to anonymize those files. That process is performed line per line and applies some filter to each line of each log and file, so the anonymization takes a long time. This heavy process during such a long time makes the instances unresponsive. Where can we touch to improve the performance?