mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 09:17:30 +03:00
c01294e8d6
Summary: This diff migrates `backsyncer_cmd` (the thing that runs in the separate backsyncer job, as opposed to bakcsyncer, triggered from push-redirector) onto `LiveCommitSyncConfig`. Specifically, this means that on every iteration of the loop, which calls `backsync_latest` we reload `CommitSyncConfig` from configerator, build a new `CommitSyncer` from it, and then pass that `CommitSyncer` to `backsync_latest`. One choice made here is to *not* create `CommitSyncer` on every iteration of the inner loop of `backsync_latest` and handle live configs outside. The reason for this is twofold: - `backsync_latest` is called form `PushRedirector` methods, and `PushRedirector` is recreated on each `unbundle` using `LiveCommitSyncConfig`. That call provides an instance of `CommitSyncer` used to push-redirect a commit we want to backsync. It seems strictly incorrect to try and maybe use a different instance. - because of some other consistency concerns (different jobs getting `CommitSyncConfig` updates at different times), any sync config change needs to go through the following loop: - lock the repo - land the change - wait some time, until all the possible queues (x-repo sync and backsync) are drained - unlock the repo - this means that it's ok to have the config refreshed outside of `backsync_latest` Reviewed By: farnz Differential Revision: D22206992 fbshipit-source-id: 83206c3ebdcb2effad7b689597a4522f9fd8148a |
||
|---|---|---|
| .. | ||
| backsyncer | ||
| benchmark | ||
| blobimport_lib | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| blobstore_sync_queue | ||
| bonsai_git_mapping | ||
| bonsai_globalrev_mapping | ||
| bonsai_hg_mapping | ||
| bookmarks | ||
| bulkops | ||
| cache_warmup | ||
| changesets | ||
| cmdlib | ||
| cmds | ||
| commit_rewriting | ||
| common | ||
| derived_data | ||
| edenapi_server | ||
| fastreplay | ||
| filenodes | ||
| filestore | ||
| git | ||
| gotham_ext | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| lfs_import_lib | ||
| lfs_protocol | ||
| lfs_server | ||
| load_limiter | ||
| manifest | ||
| megarepolib | ||
| mercurial | ||
| metaconfig | ||
| microwave | ||
| mononoke_api | ||
| mononoke_types | ||
| mutable_counters | ||
| newfilenodes | ||
| permission_checker | ||
| phases | ||
| pushrebase | ||
| reachabilityindex | ||
| repo_client | ||
| repo_import | ||
| revset | ||
| scs_server/src | ||
| segmented_changelog | ||
| server | ||
| sshrelay | ||
| tests | ||
| time_window_counter | ||
| tunables | ||
| unbundle_replay | ||
| walker | ||
| Cargo.toml | ||
| README.md | ||
Mononoke
Mononoke is a next-generation server for the Mercurial source control system, meant to scale up to accepting thousands of commits every hour across millions of files. It is primarily written in the Rust programming language.
Caveat Emptor
Mononoke is still in early stages of development. We are making it available now because we plan to start making references to it from our other open source projects.
The version that we provide on GitHub does not build yet.
This is because the code is exported verbatim from an internal repository at Facebook, and not all of the scaffolding from our internal repository can be easily extracted. The key areas where we need to shore things up are:
- Full support for a standard
cargo build. - Open source replacements for Facebook-internal services (blob store, logging etc).
The current goal is to get Mononoke working on Linux. Other Unix-like OSes may be supported in the future