[
https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-10241:
------------------------------------
Attachment: 3.0-system.log
3.0-debug.log
2.2-system.log
2.2-debug.log
I'm attaching debug.log and system.log of node3 of the following sequence of
ccm commands (2.2 and 3.0):
{noformat}
ccm create test -n 3
ccm node1 start
ccm node2 start
sleep 20
ccm stress "write n=100K cl=TWO no-warmup -schema replication(factor=2) -pop
seq=0..100K"
ccm stress "read n=100K no-warmup -pop seq=0..100K -rate threads=25"
ccm flush
ccm node3 start
sleep 60
ccm stress "write n=100K cl=TWO no-warmup -schema replication(factor=2) -pop
seq=0..100K"
sleep 10
ccm stress "read n=100K no-warmup -pop seq=0..100K -rate threads=25"
ccm node2 stop
sleep 10
ccm node2 start
ccm node3 stop
sleep 5
ccm node3 start
sleep 30
ccm node3 stop
<delete all sstables on node3>
ccm node3 start
sleep 10
ccm node1 stress "read n=1K cl=TWO no-warmup -pop seq=0..100K -rate threads=25"
ccm node1 repair
sleep 5
ccm node2 repair
ccm node1 stress "read n=1K cl=TWO no-warmup -pop seq=0..100K -rate threads=25"
ccm stop
{noformat}
The logs have the following amount of lines:
h4. 2.2
* system.log: 363
* debug.log: 928
h4. 3.0
* system.log: 537
* debug.log: 1128
> Keep a separate production debug log for troubleshooting
> --------------------------------------------------------
>
> Key: CASSANDRA-10241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10241
> Project: Cassandra
> Issue Type: New Feature
> Components: Config
> Reporter: Jonathan Ellis
> Assignee: Paulo Motta
> Fix For: 2.1.x, 2.2.x, 3.0.x
>
> Attachments: 2.2-debug.log, 2.2-system.log, 3.0-debug.log,
> 3.0-system.log
>
>
> [~aweisberg] had the suggestion to keep a separate debug log for aid in
> troubleshooting, not intended for regular human consumption but where we can
> log things that might help if something goes wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
