RaulGracia commented on issue #3466:
URL: https://github.com/apache/bookkeeper/issues/3466#issuecomment-1265261133

   Thanks a lot @dlg99, I can certainly review  #3513. But after the latest 
experiments we did with Bookkeeper 4.14.3, which includes #2794, we couldn't 
reproduce the issue, so I'm not sure that that PR is contributing to the issue 
described here. In any case, it is independent from the value that #3513 brings 
by itself. 
   
   > Can the lost ledger handle might be caused by the way Pravega handles 
errors in ledger open?
   
   The point is that the very same Pravega code has no issues using Bookkeeper 
4.14.2 client and injecting network failures, and we consistently get issues 
like the one describe here when upgrading to Bookkeeper 4.15 client. For this 
reason, I thought that the problem may be related to some change in the 
Bookkeeper client within `branch-4.15`.
   
   I think that to discar that the issue is present in the whole `branch-4.14`, 
 we will reproduce fault injection tests with latest 4.14 release; if the issue 
is cannot be reproduced, we know that `branch-4.14` is fine in this regard (and 
we do not need to inspect cherry picked PRs). If the issue is reproduced, the 
number of commits to analyze would be much smaller.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to