You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kvrocks.apache.org by "git-hulk (via GitHub)" <gi...@apache.org> on 2023/01/30 15:34:31 UTC

[GitHub] [incubator-kvrocks] git-hulk commented on issue #1235: Inconsistent error "-Can't write to slot being migrated which is in write forbidden phase"

git-hulk commented on issue #1235:
URL: https://github.com/apache/incubator-kvrocks/issues/1235#issuecomment-1408839068

   @moonsphere Thanks for your detailed explanation, I can get your point now.
   
   > forbidden_slot_ looks like an "optimism lock"
   
   Yes, you're right. We thought it was acceptable to forbid writing in a short time which mainly depends on `migrate-sequence-gap`(default is 10000 sequences). I'm not sure how long this error happens in your test case. Generally, we expected it should be <= 1s.
   
   > I guess some existed proxy(for example PegaDB proxy?) maybe can right handle this error (pending the request and wakeup when migrate command finished?)
   
   AFAIK, PegaDB didn't have the proxy to handle this error. Is that right? @ShooterIT @caipengbo @shangxiaoxiong 
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@kvrocks.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org