Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For writes to non replicated series the write should be synchronous #734

Merged
merged 1 commit into from
Jul 11, 2014

Conversation

jvshahid
Copy link
Contributor

Currently all writes go through the WAL even for non replicated time series/database. We should skip the wal if the write is not to be replicated. In that case the write is synchronous and it can pass/fail.

@pauldix
Copy link
Member

pauldix commented Jul 11, 2014

Looks like you're still writing to the WAL, which isn't necessary since the write is synchronous. I see that you added the assignSeqOnly flag to appendEntry so it seems like it's trivial to bypass the WAL based on that.

@jvshahid
Copy link
Contributor Author

Nice catch. That's fixed.

Currently all writes (unless synchronous) have to go through the write
buffer and the WAL in order to guarantee proper replication. This commit
changes the behavior for shards that aren't replicated.

Fix #734.
@pauldix
Copy link
Member

pauldix commented Jul 11, 2014

looks rad, do it!

@jvshahid jvshahid merged commit 0b6371e into master Jul 11, 2014
@jvshahid jvshahid deleted the rf-1-sync-writes branch July 11, 2014 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants