Channels should be able to be synced and updated on different servers #23

Closed
opened 2018-07-25 18:26:34 +02:00 by nikooo777 · 0 comments
nikooo777 commented 2018-07-25 18:26:34 +02:00 (Migrated from github.com)

Currently ytsync assumes that a channel is first synced and subsequently updated on the same server. This doesn't allow us to balance the load and make full use of fleets (group of temporary servers).

The following steps should be taken:

  • Remove redis dependency
  • replace current functionalities that use redis with new ones using the new synced_videos table in internal-apis
  • remove dependency of the local wallet directory and solely use the S3 storage
  • enable versioning of the wallets
  • think of an "external" lbrycrd server that feeds the ytsync servers so to avoid having to run a lbrycrd instance for all ytsync servers
Currently ytsync assumes that a channel is first synced and subsequently updated on the same server. This doesn't allow us to balance the load and make full use of fleets (group of temporary servers). The following steps should be taken: * [x] Remove redis dependency * [x] replace current functionalities that use redis with new ones using the new `synced_videos` table in internal-apis * [x] remove dependency of the local wallet directory and solely use the S3 storage * [x] enable versioning of the wallets * [x] think of an "external" lbrycrd server that feeds the ytsync servers so to avoid having to run a lbrycrd instance for all ytsync servers
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.go#23
No description provided.