[jira] [Commented] (CASSANDRA-4533) Multithreaded cache saving can skip caches

[ https://issues.apache.org/jira/browse/CASSANDRA-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434830#comment-13434830 ] Zhu Han commented on CASSANDRA-4533: Is it possible that it is fixed also in 1.0?

[jira] [Comment Edited] (CASSANDRA-4533) Multithreaded cache saving can skip caches

[ https://issues.apache.org/jira/browse/CASSANDRA-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434830#comment-13434830 ] Zhu Han edited comment on CASSANDRA-4533 at 8/15/12 5:15 PM:

[jira] [Commented] (CASSANDRA-4533) Multithreaded cache saving can skip caches

[ https://issues.apache.org/jira/browse/CASSANDRA-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435198#comment-13435198 ] Zhu Han commented on CASSANDRA-4533: Looks like we have to maintain our own fork,

[jira] [Created] (CASSANDRA-4533) Cache saving does not work

Zhu Han created CASSANDRA-4533: -- Summary: Cache saving does not work Key: CASSANDRA-4533 URL: https://issues.apache.org/jira/browse/CASSANDRA-4533 Project: Cassandra Issue Type: Bug

[jira] [Commented] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114514#comment-13114514 ] Zhu Han commented on CASSANDRA-3248: From xfs code, fsync() and fdatasync() should

[jira] [Commented] (CASSANDRA-3250) fsync the directory after new sstable or commit log segment are created

[ https://issues.apache.org/jira/browse/CASSANDRA-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114471#comment-13114471 ] Zhu Han commented on CASSANDRA-3250: On XFS, this is not a problem per the

[jira] [Created] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

CommitLog writer should call fdatasync instead of fsync --- Key: CASSANDRA-3248 URL: https://issues.apache.org/jira/browse/CASSANDRA-3248 Project: Cassandra Issue Type: Improvement

[jira] [Updated] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Han updated CASSANDRA-3248: --- Description: CommitLogSegment use SequentialWriter to flush the buffered data to log device. It

[jira] [Updated] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Han updated CASSANDRA-3248: --- Description: CommitLogSegment use SequentialWriter to flush the buffered data to log device. It

[jira] [Updated] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Han updated CASSANDRA-3248: --- Description: CommitLogSegment use SequentialWriter to flush the buffered data to log device. It

[jira] [Updated] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Han updated CASSANDRA-3248: --- Description: CommitLogSegment use SequentialWriter to flush the buffered data to log device. It

[jira] [Updated] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Han updated CASSANDRA-3248: --- Affects Version/s: 0.6.13 0.7.9 CommitLog writer should call fdatasync

[jira] [Updated] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Han updated CASSANDRA-3248: --- Description: CommitLogSegment uses SequentialWriter to flush the buffered data to log device.

[jira] [Commented] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113388#comment-13113388 ] Zhu Han commented on CASSANDRA-3248: The manual said: {quote} $man fdatasync

[jira] [Commented] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113392#comment-13113392 ] Zhu Han commented on CASSANDRA-3248: And postgresql uses fdatasync() to flush the

[jira] [Issue Comment Edited] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113388#comment-13113388 ] Zhu Han edited comment on CASSANDRA-3248 at 9/23/11 12:56 PM:

[jira] [Commented] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113437#comment-13113437 ] Zhu Han commented on CASSANDRA-3248: I checked the source code of XFS which is

[jira] [Commented] (CASSANDRA-3248) CommitLog writer should call fdatasync instead of fsync

[ https://issues.apache.org/jira/browse/CASSANDRA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113466#comment-13113466 ] Zhu Han commented on CASSANDRA-3248: It is very strange that there is no different

[jira] [Created] (CASSANDRA-3250) fsync the directory after new sstable or commit log segment are created

fsync the directory after new sstable or commit log segment are created --- Key: CASSANDRA-3250 URL: https://issues.apache.org/jira/browse/CASSANDRA-3250 Project: Cassandra

[jira] [Commented] (CASSANDRA-3250) fsync the directory after new sstable or commit log segment are created

[ https://issues.apache.org/jira/browse/CASSANDRA-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113488#comment-13113488 ] Zhu Han commented on CASSANDRA-3250: There is a relative discussion on PostgreSQL.

[jira] [Commented] (CASSANDRA-3226) Single faulty node brings down entire cluster. No reads/writes possible

[ https://issues.apache.org/jira/browse/CASSANDRA-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107835#comment-13107835 ] Zhu Han commented on CASSANDRA-3226: Thanks for the clarification. bq. Cassandra

[jira] [Commented] (CASSANDRA-3226) Single faulty node brings down entire cluster. No reads/writes possible

[ https://issues.apache.org/jira/browse/CASSANDRA-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107618#comment-13107618 ] Zhu Han commented on CASSANDRA-3226: bq. if you don't have dynamic snitch enabled

[jira] [Commented] (CASSANDRA-2434) node bootstrapping can violate consistency

[ https://issues.apache.org/jira/browse/CASSANDRA-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13097625#comment-13097625 ] Zhu Han commented on CASSANDRA-2434: bq. Also if only one node is down you should

[jira] [Commented] (CASSANDRA-2434) node bootstrapping can violate consistency

[ https://issues.apache.org/jira/browse/CASSANDRA-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13097703#comment-13097703 ] Zhu Han commented on CASSANDRA-2434: As peter suggested before, another approach

[jira] [Commented] (CASSANDRA-2434) node bootstrapping can violate consistency

[ https://issues.apache.org/jira/browse/CASSANDRA-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13096981#comment-13096981 ] Zhu Han commented on CASSANDRA-2434: Is it possible to make the node does not

[jira] [Created] (CASSANDRA-2976) Severe bug on commit log replay

Severe bug on commit log replay --- Key: CASSANDRA-2976 URL: https://issues.apache.org/jira/browse/CASSANDRA-2976 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.6.13

[jira] [Commented] (CASSANDRA-2976) Severe bug on commit log replay

[ https://issues.apache.org/jira/browse/CASSANDRA-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13073146#comment-13073146 ] Zhu Han commented on CASSANDRA-2976: For file system with coarse time resolution,

[jira] [Commented] (CASSANDRA-2976) Severe bug on commit log replay

[ https://issues.apache.org/jira/browse/CASSANDRA-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13073171#comment-13073171 ] Zhu Han commented on CASSANDRA-2976: Oh, I just forgot the conflict resolution is

[jira] [Resolved] (CASSANDRA-2976) Severe bug on commit log replay

[ https://issues.apache.org/jira/browse/CASSANDRA-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Han resolved CASSANDRA-2976. Resolution: Won't Fix It is not necessary to maintain the order during log replay, as conflict

[jira] [Commented] (CASSANDRA-2829) memtable with no post-flush activity can leave commitlog permanently dirty

[ https://issues.apache.org/jira/browse/CASSANDRA-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13073180#comment-13073180 ] Zhu Han commented on CASSANDRA-2829: {quote}Let's add that information and fix

[jira] [Commented] (CASSANDRA-2829) memtable with no post-flush activity can leave commitlog permanently dirty

[ https://issues.apache.org/jira/browse/CASSANDRA-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13073320#comment-13073320 ] Zhu Han commented on CASSANDRA-2829: {quote}This can be kept purely

[jira] [Commented] (CASSANDRA-2868) Native Memory Leak

[ https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066376#comment-13066376 ] Zhu Han commented on CASSANDRA-2868: Got it! Do you have any idea why only some

[jira] [Issue Comment Edited] (CASSANDRA-2868) Native Memory Leak

[ https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066009#comment-13066009 ] Zhu Han edited comment on CASSANDRA-2868 at 7/15/11 3:33 PM:

[jira] [Commented] (CASSANDRA-2868) Native Memory Leak

[ https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066009#comment-13066009 ] Zhu Han commented on CASSANDRA-2868: {We have been running this in production for

[jira] [Issue Comment Edited] (CASSANDRA-2868) Native Memory Leak

[ https://issues.apache.org/jira/browse/CASSANDRA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066009#comment-13066009 ] Zhu Han edited comment on CASSANDRA-2868 at 7/15/11 3:35 PM:

[jira] Updated: (CASSANDRA-1592) Apply regular expression to row keys

[ https://issues.apache.org/jira/browse/CASSANDRA-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhu han updated CASSANDRA-1592: --- Attachment: cassandra-0.7.0-beta2_key_regex.patch Apply regular expression to row keys

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919464#action_12919464 ] zhu han commented on CASSANDRA-1546: Kelvin, Thanks for clarification. It is a

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919453#action_12919453 ] zhu han commented on CASSANDRA-1546: {quote} I wasn't clear in the last

[jira] Created: (CASSANDRA-1592) Apply regular expression to row keys

Apply regular expression to row keys Key: CASSANDRA-1592 URL: https://issues.apache.org/jira/browse/CASSANDRA-1592 Project: Cassandra Issue Type: New Feature Components: API

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919143#action_12919143 ] zhu han commented on CASSANDRA-1546: {quote} I think it's worth it for you to

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915712#action_12915712 ] zhu han commented on CASSANDRA-1546: {quote} So, to answer the question about

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915276#action_12915276 ] zhu han commented on CASSANDRA-1546: That's soo cool. Thank you. :-) Does the

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915352#action_12915352 ] zhu han commented on CASSANDRA-1546: Thank you for you detailed response. {quote}

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915588#action_12915588 ] zhu han commented on CASSANDRA-1546: {quote} Streaming/repair will only be broken

[jira] Commented: (CASSANDRA-1546) (Yet another) approach to counting

[ https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915597#action_12915597 ] zhu han commented on CASSANDRA-1546: One more question on the local counter column.

[jira] Commented: (CASSANDRA-1502) remove IClock from internals

[ https://issues.apache.org/jira/browse/CASSANDRA-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915103#action_12915103 ] zhu han commented on CASSANDRA-1502: Seems like we have not found a solution