[
https://issues.apache.org/jira/browse/CASSANDRA-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Harvey updated CASSANDRA-4492:
------------------------------------
Description:
Running into an issue on a 6 node ring running 1.0.11 where whenever a somewhat
large set of hints build up (seen as low as 400MB), compaction on the hints CF
hangs indefinitely. Nothing of note in the logs. In some cases, the compaction
hangs before a tmp sstable is even created.
I've wiped out every hints sstable I have and restarted several times. The
issue always comes back rather quickly and predictably after wiping the
sstables. Compaction always seems to succeed if the hints CFs are rather small.
Hints are enabled, and my hint window is the default of 1hr. I do have some
copies of HintsColumnFamily sstables that do replicate this issue. However, the
hints may contain confidential data. If they'd be helpful in troubleshooting
this issue, let me know and I can see about sending them directly.
This ring was upgraded from 1.0.7. I didn't keep any hints from the upgrade.
Here is the output I see from compactionstats where a compaction has hung. The
'bytes compacted' column never changes.
{code}
pending tasks: 1
compaction type keyspace column family bytes compacted
bytes total progress
Compaction systemHintsColumnFamily 268082
464784758 0.06%
{code}
was:
Running into an issue on a 6 nodes 1.0.11 ring where whenever a somewhat large
set of hints build up (seen as low as 400MB), compaction on the hints CF hangs
indefinitely. Nothing of note in the logs. In some cases, the compaction hangs
before a tmp sstable is even created.
I've wiped out every hints sstable I have and restarted several times. The
issue always comes back rather quickly and predictably after wiping the
sstables. Compaction always seems to succeed if the hints CFs are rather small.
Hints are enabled, and my hint window is the default of 1hr. I do have some
copies of HintsColumnFamily sstables that do replicate this issue. However, the
hints may contain confidential data. If they'd be helpful in troubleshooting
this issue, let me know and I can see about sending them directly.
This ring was upgraded from 1.0.7. I didn't keep any hints from the upgrade.
Here is the output I see from compactionstats where a compaction has hung. The
'bytes compacted' column never changes.
{code}
pending tasks: 1
compaction type keyspace column family bytes compacted
bytes total progress
Compaction systemHintsColumnFamily 268082
464784758 0.06%
{code}
> Large HintsColumnFamily compactions hang
> ----------------------------------------
>
> Key: CASSANDRA-4492
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4492
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.11
> Reporter: Jason Harvey
> Priority: Minor
>
> Running into an issue on a 6 node ring running 1.0.11 where whenever a
> somewhat large set of hints build up (seen as low as 400MB), compaction on
> the hints CF hangs indefinitely. Nothing of note in the logs. In some cases,
> the compaction hangs before a tmp sstable is even created.
> I've wiped out every hints sstable I have and restarted several times. The
> issue always comes back rather quickly and predictably after wiping the
> sstables. Compaction always seems to succeed if the hints CFs are rather
> small.
> Hints are enabled, and my hint window is the default of 1hr. I do have some
> copies of HintsColumnFamily sstables that do replicate this issue. However,
> the hints may contain confidential data. If they'd be helpful in
> troubleshooting this issue, let me know and I can see about sending them
> directly.
> This ring was upgraded from 1.0.7. I didn't keep any hints from the upgrade.
> Here is the output I see from compactionstats where a compaction has hung.
> The 'bytes compacted' column never changes.
> {code}
> pending tasks: 1
> compaction type keyspace column family bytes compacted
> bytes total progress
> Compaction systemHintsColumnFamily 268082
> 464784758 0.06%
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
