Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Dispatcher can issue a migration request that comes back as failed even though it succeeded #24

Open
Assignees
jungkumseok
@marusshi

Description

@marusshi

Let's say we want to migrateFoo fromPi0 toPi1, using Dispatcher.

The current protocol is then:

  1. Dispatcher sends pubsub message toPi0 (migrate Foo)
  2. Pi0 sends pubsub message toPi1 (run my snapshot of Foo)
  3. Foo successfully migrated toPi1
  4. Pi1 sends an ACK back toPi0
  5. Pi0 sends ACK back to Dispatcher (your request was successful)

IfPi0 dies after step 3 but before step 5, Dispatcher will never receive an ACK, the migrate request will timeout and the user will think the migration failed even though it succeeded.
Maybe instead of listening for an ACK fromPi0, should Dispatcher listen for ACK fromPi1?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp