[jira] [Commented] (CASSANDRA-15755) Add a debug line informing of building summary during sstable open

2020-05-06 Thread Dinesh Joshi (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101204#comment-17101204
 ] 

Dinesh Joshi commented on CASSANDRA-15755:
--

thanks [~sumanth.pasupuleti]. Looks like the the {{ViewTest}} is flaky. It 
passed after a few tries.

> Add a debug line informing of building summary during sstable open
> --
>
> Key: CASSANDRA-15755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15755
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability/Logging
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Low
> Fix For: 4.x
>
> Attachments: 15755-4.0.txt
>
>
> We've had a situation where our backup-restore flow did not include 
> summary.db component for a large file with a lot of keys. This caused 
> Cassandra on the restored node to take a long time to boot (while it was 
> building the summary).
> The last message was about opening a few sstables. It would be nice to also 
> include a debug line about building summary, which then operators can use to 
> check if a missing summary file is expected. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15755) Add a debug line informing of building summary during sstable open

2020-05-06 Thread Sumanth Pasupuleti (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101172#comment-17101172
 ] 

Sumanth Pasupuleti commented on CASSANDRA-15755:


+1 [~djoshi]!

> Add a debug line informing of building summary during sstable open
> --
>
> Key: CASSANDRA-15755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15755
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability/Logging
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Low
> Fix For: 4.x
>
> Attachments: 15755-4.0.txt
>
>
> We've had a situation where our backup-restore flow did not include 
> summary.db component for a large file with a lot of keys. This caused 
> Cassandra on the restored node to take a long time to boot (while it was 
> building the summary).
> The last message was about opening a few sstables. It would be nice to also 
> include a debug line about building summary, which then operators can use to 
> check if a missing summary file is expected. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15755) Add a debug line informing of building summary during sstable open

2020-05-06 Thread Dinesh Joshi (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101099#comment-17101099
 ] 

Dinesh Joshi commented on CASSANDRA-15755:
--

Hi [~sumanth.pasupuleti] thanks for the patch. Overall it looks good. I've 
added some minor changes to it. Let me know if they're good and I'll commit it.

[trunk|https://github.com/dineshjoshi/cassandra/tree/15755-trunk] 
[CI|https://circleci.com/workflow-run/67d85eed-e46e-4066-b95c-7ddb60b9e799]

> Add a debug line informing of building summary during sstable open
> --
>
> Key: CASSANDRA-15755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15755
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability/Logging
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Low
> Fix For: 4.x
>
> Attachments: 15755-4.0.txt
>
>
> We've had a situation where our backup-restore flow did not include 
> summary.db component for a large file with a lot of keys. This caused 
> Cassandra on the restored node to take a long time to boot (while it was 
> building the summary).
> The last message was about opening a few sstables. It would be nice to also 
> include a debug line about building summary, which then operators can use to 
> check if a missing summary file is expected. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15755) Add a debug line informing of building summary during sstable open

2020-04-23 Thread Sumanth Pasupuleti (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091056#comment-17091056
 ] 

Sumanth Pasupuleti commented on CASSANDRA-15755:


[~djoshi] attached the patch. Haven't made any changes to CHANGES.txt since 
this is a minor change of adding a couple of debug logs.

> Add a debug line informing of building summary during sstable open
> --
>
> Key: CASSANDRA-15755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15755
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability/Logging
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Low
> Fix For: 4.x
>
> Attachments: 15755-4.0.txt
>
>
> We've had a situation where our backup-restore flow did not include 
> summary.db component for a large file with a lot of keys. This caused 
> Cassandra on the restored node to take a long time to boot (while it was 
> building the summary).
> The last message was about opening a few sstables. It would be nice to also 
> include a debug line about building summary, which then operators can use to 
> check if a missing summary file is expected. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15755) Add a debug line informing of building summary during sstable open

2020-04-23 Thread Sumanth Pasupuleti (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090814#comment-17090814
 ] 

Sumanth Pasupuleti commented on CASSANDRA-15755:


[~djoshi] Absolutely. Made a simple patch internally for adding the log line. 
Will send a patch out soon.

> Add a debug line informing of building summary during sstable open
> --
>
> Key: CASSANDRA-15755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15755
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability/Logging
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Low
> Fix For: 4.x
>
>
> We've had a situation where our backup-restore flow did not include 
> summary.db component for a large file with a lot of keys. This caused 
> Cassandra on the restored node to take a long time to boot (while it was 
> building the summary).
> The last message was about opening a few sstables. It would be nice to also 
> include a debug line about building summary, which then operators can use to 
> check if a missing summary file is expected. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15755) Add a debug line informing of building summary during sstable open

2020-04-23 Thread Dinesh Joshi (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090776#comment-17090776
 ] 

Dinesh Joshi commented on CASSANDRA-15755:
--

[~sumanth.pasupuleti], do you want to send a patch for what you're expecting in 
the logs?

> Add a debug line informing of building summary during sstable open
> --
>
> Key: CASSANDRA-15755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15755
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability/Logging
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Low
> Fix For: 4.x
>
>
> We've had a situation where our backup-restore flow did not include 
> summary.db component for a large file with a lot of keys. This caused 
> Cassandra on the restored node to take a long time to boot (while it was 
> building the summary).
> The last message was about opening a few sstables. It would be nice to also 
> include a debug line about building summary, which then operators can use to 
> check if a missing summary file is expected. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org