[ 
https://issues.apache.org/jira/browse/CASSANDRA-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-21624:
-----------------------------------------
    Attachment: results_details_apache_5.0_202.tar.xz
                ci_summary_apache_5.0_202.html

> Reduce CI console output volume
> -------------------------------
>
>                 Key: CASSANDRA-21624
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21624
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: CI
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 5.0.x, 6.0.x, 7.x
>
>         Attachments: ci_summary_apache_5.0_202.html, 
> results_details_apache_5.0_202.tar.xz
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Analysis of a [Jenkins console 
> log|https://ci-cassandra.apache.org/job/Cassandra-5.0/654/] shows ~43MB (41%) 
> is two classes of pure-noise output that stream through the controller and 
> are buffered in the controller heap per the in-flight sh step:
> * Python dtest runs stream the cassandra-driver's reconnect loop at DEBUG 
> level. A single flapping dtest-novnode cell produced 14,875 full Python 
> tracebacks (~22MB) plus ~80k cassandra.cluster log lines (~11MB), peak 
> 4.2MB/min.
>                                                                               
>                                                                               
>                                                                               
>   * Every forked test JVM logs the complete ant command line including the 
> full ~17KB classpath ("Forking using command: [...]") = 1,296 lines = 21.4MB, 
> identical content every time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to