[jira] [Created] (CASSANDRA-15179) multiple validation compactions on single table
Nathan Jackels created CASSANDRA-15179:
--
Summary: multiple validation compactions on single table
Key: CASSANDRA-15179
URL: https://issues.apache.org/jira/browse/CASSANDRA-15179
Project: Cassandra
Issue Type: Bug
Components: Consistency/Repair
Reporter: Nathan Jackels
Attachments: coordinator_log.txt, non_coordinator_log.txt,
repair_coordinator_console.txt
In a 2 node cluster I'm observing that after a repair is started, any repairs
started leaves validation compactions running on the coordinator node.
The non-coordinator correctly rejects the repair with
{noformat}ActiveRepairService.java:525 - Cannot start multiple repair sessions
over the same sstables{noformat} but the coordinator did not. When testing to
confirm the behavior I was able to increase the executing validations from 11
to ~18 running on the same table and an additional 17 [compactions] pending
with high confidence they were pending validations. (see attached scrubbed
files).
Repairs were started with: nodetool repair -- keyspace_01 table_02
Initially I thought this might be fixed with CASSANDRA-14332, but that is a
revert of changes from CASSANDRA-13797 which was released in 3.0.15 and I'm
running 3.0.10 so shouldn't be affected. So far in the ~1.5 hours since
noticing this I haven't been able to recreate the issue.
I'm will soon be validating 3.0.18 and will retest with that release if I can
figure out how to recreate.
Environment Info:
* Cassandra 3.0.10
* 10.0.0.1: Windows 10 / 4C8T / 16 GB DDR4 / JRE 1.8.191
* 10.0.0.2: Windows 7 / 4C8T / 16 GB DDR3 / JRE 1.8.191
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15174) some utils do not run on windows with default bat scripts
[
https://issues.apache.org/jira/browse/CASSANDRA-15174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Jackels updated CASSANDRA-15174:
---
Description:
The following scripts in tools/bin do not pass %CASSANDRA_PARAMS% to the jvm
which prevent successful execution because cassandra.storagedir is not set.
* sstablemetadata.bat
* sstableexpiredblockers.bat
{noformat}
> sstablemetadata.bat
> D:\data\system\local-7ad54392bcdd35a684174e047860b377\mc-1288-big-Data.db
...
INFO 03:05:35 Loaded cassandra-topology.properties for compatibility
Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered
during startup: hints_directory is missing and -Dcassandra.storagedir is not set
hints_directory is missing and -Dcassandra.storagedir is not set
{noformat}
observed with 3.0.10
was:
The following scripts in tools/bin do not pass %CASSANDRA_PARAMS% to the jvm
which prevent successful execution because cassandra.storagedir is not set.
* sstablemetadata.bat
* sstableexpiredblockers.bat
{noformat}
> sstablemetadata.bat
> D:\data\system\local-7ad54392bcdd35a684174e047860b377\mc-1288-big-Data.db
...
INFO 03:05:35 Loaded cassandra-topology.properties for compatibility
Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered
during startup: hints_directory is missing and -Dcassandra.storagedir is not set
hints_directory is missing and -Dcassandra.storagedir is not set
{noformat}
> some utils do not run on windows with default bat scripts
> -
>
> Key: CASSANDRA-15174
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15174
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/sstable
>Reporter: Nathan Jackels
>Priority: Normal
>
> The following scripts in tools/bin do not pass %CASSANDRA_PARAMS% to the jvm
> which prevent successful execution because cassandra.storagedir is not set.
> * sstablemetadata.bat
> * sstableexpiredblockers.bat
> {noformat}
> > sstablemetadata.bat
> > D:\data\system\local-7ad54392bcdd35a684174e047860b377\mc-1288-big-Data.db
> ...
> INFO 03:05:35 Loaded cassandra-topology.properties for compatibility
> Exception (org.apache.cassandra.exceptions.ConfigurationException)
> encountered during startup: hints_directory is missing and
> -Dcassandra.storagedir is not set
> hints_directory is missing and -Dcassandra.storagedir is not set
> {noformat}
> observed with 3.0.10
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15174) some utils do not run on windows with default bat scripts
[
https://issues.apache.org/jira/browse/CASSANDRA-15174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Jackels updated CASSANDRA-15174:
---
Description:
The following scripts in tools/bin do not pass %CASSANDRA_PARAMS% to the jvm
which prevent successful execution because cassandra.storagedir is not set.
* sstablemetadata.bat
* sstableexpiredblockers.bat
{noformat}
> sstablemetadata.bat
> D:\data\system\local-7ad54392bcdd35a684174e047860b377\mc-1288-big-Data.db
...
INFO 03:05:35 Loaded cassandra-topology.properties for compatibility
Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered
during startup: hints_directory is missing and -Dcassandra.storagedir is not set
hints_directory is missing and -Dcassandra.storagedir is not set
{noformat}
was:
The following scripts in tools/bin do not pass %CASSANDRA_PARAMS% to the jvm
which prevent successful execution because cassandra.storagedir is not set.
* sstablemetadata.bat
* sstableexpiredblockers.bat
> some utils do not run on windows with default bat scripts
> -
>
> Key: CASSANDRA-15174
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15174
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/sstable
>Reporter: Nathan Jackels
>Priority: Normal
>
> The following scripts in tools/bin do not pass %CASSANDRA_PARAMS% to the jvm
> which prevent successful execution because cassandra.storagedir is not set.
> * sstablemetadata.bat
> * sstableexpiredblockers.bat
> {noformat}
> > sstablemetadata.bat
> > D:\data\system\local-7ad54392bcdd35a684174e047860b377\mc-1288-big-Data.db
> ...
> INFO 03:05:35 Loaded cassandra-topology.properties for compatibility
> Exception (org.apache.cassandra.exceptions.ConfigurationException)
> encountered during startup: hints_directory is missing and
> -Dcassandra.storagedir is not set
> hints_directory is missing and -Dcassandra.storagedir is not set
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15174) some utils do not run on windows with default bat scripts
Nathan Jackels created CASSANDRA-15174: -- Summary: some utils do not run on windows with default bat scripts Key: CASSANDRA-15174 URL: https://issues.apache.org/jira/browse/CASSANDRA-15174 Project: Cassandra Issue Type: Improvement Components: Tool/sstable Reporter: Nathan Jackels The following scripts in tools/bin do not pass %CASSANDRA_PARAMS% to the jvm which prevent successful execution because cassandra.storagedir is not set. * sstablemetadata.bat * sstableexpiredblockers.bat -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15173) fix log for inconsistent-left-subrange in merkle-tree
[
https://issues.apache.org/jira/browse/CASSANDRA-15173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868203#comment-16868203
]
Nathan Jackels commented on CASSANDRA-15173:
Created [pull request #327|https://github.com/apache/cassandra/pull/327]
> fix log for inconsistent-left-subrange in merkle-tree
> -
>
> Key: CASSANDRA-15173
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15173
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Streaming and Messaging
>Reporter: Nathan Jackels
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> One of the logs added in CASSANDRA-13052 is called with incorrect arguments.
> In org.apache.cassandra.utils.MerkleTree::differenceHelper the right-side
> subrange logs with right:
> {code:java}
> else if (!rreso)
> {
> logger.debug("({}) Right sub-range fully inconsistent {}",
> active.depth, right);
> rdiff = FULLY_INCONSISTENT;
> }
> {code}
> but left side is also (incorrectly) logged with right:
> {code:java}
> else if (!lreso)
> {
> logger.debug("({}) Left sub-range fully inconsistent {}",
> active.depth, right);
> ldiff = FULLY_INCONSISTENT;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15173) fix log for inconsistent-left-subrange in merkle-tree
Nathan Jackels created CASSANDRA-15173:
--
Summary: fix log for inconsistent-left-subrange in merkle-tree
Key: CASSANDRA-15173
URL: https://issues.apache.org/jira/browse/CASSANDRA-15173
Project: Cassandra
Issue Type: Improvement
Components: Legacy/Streaming and Messaging
Reporter: Nathan Jackels
One of the logs added in CASSANDRA-13052 is called with incorrect arguments.
In org.apache.cassandra.utils.MerkleTree::differenceHelper the right-side
subrange logs with right:
{code:java}
else if (!rreso)
{
logger.debug("({}) Right sub-range fully inconsistent {}",
active.depth, right);
rdiff = FULLY_INCONSISTENT;
}
{code}
but left side is also (incorrectly) logged with right:
{code:java}
else if (!lreso)
{
logger.debug("({}) Left sub-range fully inconsistent {}", active.depth,
right);
ldiff = FULLY_INCONSISTENT;
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-13605) threads created during classload-static sections open commitlog handles
Nathan Jackels created CASSANDRA-13605:
--
Summary: threads created during classload-static sections open
commitlog handles
Key: CASSANDRA-13605
URL: https://issues.apache.org/jira/browse/CASSANDRA-13605
Project: Cassandra
Issue Type: Bug
Components: Core, Tools
Reporter: Nathan Jackels
Priority: Minor
Fix For: 3.0.x
Some classes, such as org.apache.cassandra.db.commitlog.CommitLog create
threads in static blocks. Some of these threads then open file-descriptors for
the commitlog (and possibly sstables).
{noformat}
...
public static final CommitLog instance = CommitLog.construct();
...
private static CommitLog construct()
{
CommitLog log = new CommitLog(DatabaseDescriptor.getCommitLogLocation(),
CommitLogArchiver.construct());
return log.start();
}
...
{noformat}
If this occurs in a non-daemon process such as nodetool, or any of the other
sstable tools it could prevent a CassandraDaemon from deleting commitlog files.
These threads should only open files automatically if the process is a
CassandraDaemon, not if it's a utility.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
