[
https://issues.apache.org/jira/browse/CASSANDRA-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joaquin Casares updated CASSANDRA-4570:
---------------------------------------
Attachment: info_paths_v2.txt
mt_compaction_v2.txt
jvm_warnings_v2.txt
jvm_warnings_v2:
Now only checks the 1.6.0 releases. Updated the minor revision numbers to be in
line with what we're currently seeing.
mt_compaction_v2:
Moved this to DatabaseDescriptor where it should be.
info_paths_v2:
Now displaying this shortly after the yaml path is printed.
check_tables (original):
Nope, this only logs once. The issue before was that it was always logging
"Found table data in data directories. Consider using the CQL shell to define
your schema."
With the patch: http://aep.appspot.com/display/xITUgvlTOPjfmCnL_ns6tkXhZ1s/
Without: http://aep.appspot.com/display/6ffn0ucc0pCEHS53p6nX9J0sgnM/
Probably due to: Schema.instance.addSystemTable(systemMeta);
being run before loadSchemas().
> Minor logging additions
> -----------------------
>
> Key: CASSANDRA-4570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4570
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.1.4
> Reporter: Joaquin Casares
> Assignee: Joaquin Casares
> Priority: Trivial
> Attachments: check_tables.txt, info_paths.txt, info_paths_v2.txt,
> jvm_warnings.txt, jvm_warnings_v2.txt, mt_compaction.txt, mt_compaction_v2.txt
>
>
> Four patches to clear up/add information to logging.
> 1. check_tables
> Moves a portion of the code that checks for data files to right before the
> system tables are created.
> 2. info_paths
> Adds path printing statements for the cassandra.yaml, data_dir, and
> commit_log locations.
> 3. jvm_warnings
> Warn the user if they are on OpenJDK.
> Warn the user if they are using a minor version < 29.
> Error if they are using a minor version < 25.
> 4. mt_compaction
> Log that the user is performing compactions with multi-threaded compactions
> enabled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
