[
https://issues.apache.org/jira/browse/CASSANDRA-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862260#comment-13862260
]
Lyuben Todorov commented on CASSANDRA-6456:
-------------------------------------------
A few more that can be removed (with arguments for keeping some of them):
- DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap - should
be kept.
- Global memtable threshold is enabled at 502MB - only shows up in {{config = [
... ]}} if we've uncommented {{memtable_total_space_in_mb}} in cassandra.yaml
- Initializing key cache with capacity of 100 MBs - Should be kept, logs info
even if {{key_cache_size_in_mb=null}} showing the default setting (100 mb)
- Scheduling key cache save to each 14400 seconds (going to save all keys) -
This can go (covered by {{key_cache_save_period=14400}})
- Initializing row cache with capacity of 0 MB - Not sure on this one, default
is 0 but it can be set to null as well
- Scheduling row cache save to each 0 seconds (going to save all keys) - This
can go (covered by {{row_cache_save_period=0}})
- Starting Messaging Service on port 7000 - Users still need to know that
messaging service has started.
- Node localhost/127.0.0.1 state jump to normal - Users still need to know that
node has achieved normal state
- Starting listening for CQL clients on localhost/127.0.0.1:9042... - Its good
to users the interface is available
- Using TFramedTransport with a max frame size of 15728640 bytes. - This can go
(covered by {{thrift_framed_transport_size_in_mb=15}})
- Binding thrift service to localhost/127.0.0.1:9160 - Again, good to tell
users about interface availability status
- Using synchronous/threadpool thrift server on localhost : 9160 - This can go
(covered by {{rpc_server_type=sync}})
And when running with DEBUG:
- DEBUG 23:59:21 setting auto_bootstrap to true - This can go (covered by
{{auto_snapshot=true}})
> log listen address at startup
> -----------------------------
>
> Key: CASSANDRA-6456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6456
> Project: Cassandra
> Issue Type: Wish
> Components: Core
> Reporter: Jeremy Hanna
> Assignee: Sean Bridges
> Priority: Trivial
> Attachments: CASSANDRA-6456-2.patch, CASSANDRA-6456.patch
>
>
> When looking through logs from a cluster, sometimes it's handy to know the
> address a node is from the logs. It would be convenient if on startup, we
> indicated the listen address for that node.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
