GithubHelp home page GithubHelp logo

Comments (7)

estebangarcia avatar estebangarcia commented on May 20, 2024

We have that exact same error with bookkeeper's autorecovery.

from pulsar.

sschepens avatar sschepens commented on May 20, 2024

@merlimat do you know if this is normal?

from pulsar.

merlimat avatar merlimat commented on May 20, 2024

@sschepens @estebangarcia How did you enabled the auto-recovery?

There are a couple of ways to run the replication workers:

  1. In the same JVM process as the bookies autoRecoveryDaemonEnabled=true in conf/bookkeeper.conf
  2. As a separate process running either on every bookie, or just in a few VMs. It can be started with
    bin/bookkeeper autorecovery

In both cases, the replication workers will watch for bookies that are not available and will
trigger the copy of all data that was stored in the bookie (from another available replica).

You can check the status of under-replicated ledgers with :

bin/bookkeeper shell listunderreplicated 

For errors in broker logs, that is somewhat expected, if the ledgers are still under-replicated the client is trying to read them from the failed bookie. Though, even when data is already replicated, the BK client might not see the metadata change unless there is a read-error, so it can be printing a bit of error logs.

We still have the pending task to backport a patch from Twitter branch to include read sequence reordering. That would make the client to first try to read from bookies that are marked available in ZK,

from pulsar.

sschepens avatar sschepens commented on May 20, 2024

We did run separate autorecovery processes using bin/bookkeeper autorecovery but the failed consistently with connection errors to the failed broker.
We also saw a lot of underreplicated ledgers, but the autorecovery processes never managed to empty it, because they failed connecting to the failed broker, which makes little sense.

from pulsar.

merlimat avatar merlimat commented on May 20, 2024

I don't know if that's the case, though the auto-recovery workers to be running when you shutdown the bookie, otherwise they won't notice the unavailable bookie.

There is later a full check for under-replicated ledgers that runs once a day.

from pulsar.

ivankelly avatar ivankelly commented on May 20, 2024

@sschepens is this still an issue?

from pulsar.

ivankelly avatar ivankelly commented on May 20, 2024

Closing due to lack of activity.

from pulsar.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.