cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13873) Ref bug in Scrub
Date Thu, 30 Nov 2017 08:41:00 GMT


Marcus Eriksson commented on CASSANDRA-13873:

bq. Splitter/Upgrader, but since they're offline
yeah, don't think we need it here, we don't open early when doing offline operations and we
should have no concurrent operations referencing sstables

bq. I also don't see anything in anticompaction grabbing a ref;
looks like we do it [here|]

I'll prepare the patches and start the dtests

> Ref bug in Scrub
> ----------------
>                 Key: CASSANDRA-13873
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: T Jake Luciani
>            Assignee: Joel Knighton
>             Fix For: 2.2.x, 3.0.x, 3.11.x, 4.x
> I'm hitting a Ref bug when many scrubs run against a node.  This doesn't happen on 3.0.X.
 I'm not sure if/if not this happens with compactions too but I suspect it does.
> I'm not seeing any Ref leaks or double frees.
> To Reproduce:
> {quote}
> ./tools/bin/cassandra-stress write n=10m -rate threads=100
> ./bin/nodetool scrub
> #Ctrl-C
> ./bin/nodetool scrub
> #Ctrl-C
> ./bin/nodetool scrub
> #Ctrl-C
> ./bin/nodetool scrub
> {quote}
> Eventually in the logs you get:
> WARN  [RMI TCP Connection(4)-] 2017-09-14 15:51:26,722
- Spinning trying to capture readers [BigTableReader(path='/home/jake/workspace/cassandra2/data/data/keyspace1/standard1-2eb5c780998311e79e09311efffdcd17/mc-5-big-Data.db'),
> *released: [BigTableReader(path='/home/jake/workspace/cassandra2/data/data/keyspace1/standard1-2eb5c780998311e79e09311efffdcd17/mc-5-big-Data.db')],*

> This released table has a selfRef of 0 but is in the Tracker

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message