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.

Sign up for GitHub

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

Jump to bottom

Distributed RocksDB: Data sync & file lock #30

Open
rockeet opened this issue Oct 13, 2018 · 0 comments
Open

Distributed RocksDB: Data sync & file lock #30

rockeet opened this issue Oct 13, 2018 · 0 comments
Assignees
@luantian-terark
Labels
Distributed RocksDB

Comments

@rockeet
Copy link
Member

rockeet commented Oct 13, 2018 •
edited
Loading

There are two kind of readonly readers, syncing-readonly and nonsyncing-readonly.

  1. Writer publish DB changes: wal-log, manifest...
  2. When a readonly node is up
    1. it need to connect to writer node to acquire a snapshot.
      • if writer is not online, ...
      • any way, it needs some mechanism to lock needed files(prevent such files being deleted)
    2. if it is syncing-readonly, it subscribe topics for DB changes
    3. if it is nonsyncing-readonly, it just do read
  3. using ZooKeeper
  • 2018-10-18 10:57: In gluster-env implementation, create a sync-channel for log files: file name pattern is log, we create such a sync-channel, this may be simplify the overall implementation.
@rockeet rockeet changed the title Distributed RocksDB: Use ZeroMQ for event passing Distributed RocksDB: Data sync & file lock Oct 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luantian-terark luantian-terark

Labels
Distributed RocksDB
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rockeet @luantian-terark