Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jordan Zimmerman
    @Randgalt
    Enrico Olivelli
    @eolivelli
    @anmolnar @nkalmar I have problems with my linux laptop (broken hard disk....) I won't be able to cut a new RC until the weekend
    Andor Molnár
    @anmolnar
    @eolivelli I can do that
    this evening or tomorrow
    @Randgalt awesome!
    Jordan Zimmerman
    @Randgalt
    Did anyone see my question re persistent watches? "Question: what should happen when a PersistentWatcher is set on a node that exists? Should it immediately send a NodeCreated event like an exists event does?"
    Right now it does nothing which seems fine to me - but it's debatable
    Andor Molnár
    @anmolnar
    @Randgalt not many people from the community actively monitoring this channel. I think it’s better to discuss details on the pull request itself.
    I think it’s fine as it is now
    fatemeeeeeee
    @fatemeeeeeee
    hello,i have a question : is it possible to set up multi zookeeper brokers on single machine(node)?
    Andor Molnár
    @anmolnar
    @fatemeeeeeee yes. you can configure them to listen on different ports
    Jordan Zimmerman
    @Randgalt
    Congrats on 3.5.6 everyone. Now that that’s out what about ZOOKEEPER-
    ZOOKEEPER-1416
    Andor Molnár
    @anmolnar
    I’m looking
    Jordan Zimmerman
    @Randgalt
    👍
    Jordan Zimmerman
    @Randgalt
    Andor (et al). For Persistent Watches, I’m assuming all operations for a given client are serialized. That’s correct? I want to make sure that once a Persistent Watcher is set the client will not miss events. i.e. T1: set the watch; T2: multiple clients set data on a watched path; T3: our client calls getData. While processing the getData multiple clients call setData on the node. I believe that the server will queue up multiple watch triggers for the client and the client will see them in order after its getData completes.
    Jordan Zimmerman
    @Randgalt
    (Note T(n) above is time)
    Andor Molnár
    @anmolnar
    @Randgalt
    join the slack channel
    As I heard it’s open for everybody now with a free invite (not just committers)
    I think we should use it instead of Gitter
    regarding your question: looks like it’s not serialized. e.g. if a watcher gets triggered during the processing of getData() request, the result of watcher will be queued before getData() response
    both will end up calling sendResponse() on the connection
    Jordan Zimmerman
    @Randgalt
    What's the address for ZooKeeper slack?
    Andor Molnár
    @anmolnar
    I sent you an invite
    it’s basically the official ASF Slack / #zookeeper channel
    Jordan Zimmerman
    @Randgalt
    Oh. I can access that. I’ll join
    maheswar4b4
    @maheswar4b4
    Hi,
    Does zookeeper provide methods to configure serializer and deserializer for the data of znode ?
    Andor Molnár
    @anmolnar
    @maheswar4b4 nope.
    Jordan Zimmerman
    @Randgalt
    @maheswar4b4 Apache Curator supports this
    maheswar4b4
    @maheswar4b4
    @Randgalt Thanks, I will check curator then
    walker
    @lwx2615
    hi,everyone
    walker
    @lwx2615
    the log4j said" Define some default values that can be overridden by system properties",but how to overridden it
    I can't see any log config in the zoo.cfg
    walker
    @lwx2615
    I have got it at other file
    frid
    @FridMehdi
    @hello Folks some one could explain this issue "This ZooKeeper instance is not currently serving requests"
    Jordan Zimmerman
    @Randgalt
    It means your ensemble is not in Quroum. E.g. you have a 3 instance ensemble and 2 instances are down
    enixon
    @enixon
    @lwx2615 you can override logging properties by passing java args into the process, for example '-Dlog4j.configuration=' can be used to specify a custom logging config file. This cannot be set through the zookeeper configuration file.
    @FridMehdi any instance responding with "not currently serving requests" is not connected to the ensemble leader (possibly because there isn't one but also if there's some network partition).
    walker
    @lwx2615
    @enixon thank you!
    namnhcntt
    @namnhcntt
    Hi everyone, I faced issue with zookeeper in docker: "Refusing session request for client /10.255.0.2:42078 as it has seen zxid 0x1b0000001b our last zxid is 0x1b0000001a client must try another server". Please help me resolve this issue, thanks
    image.png
    enixon
    @enixon
    @namnhcntt , you'd see this error message if a client has disconnected from an active zookeeper server and is attempting to reconnect to another server in the ensemble that is lagging behind. I'd expect that the session timeout at the client (how long it's disconnected before trying the next server) would be more than any server lag you might be seeing in the quorum but these are both avenues to explore. Try seeing if any of your servers are experiencing extensive lag compared to the others or if your session timeout on the client is set too low.
    yctn
    @yctn
    i rebooted one of my zookeeper nodes but it refuses to join. so i restart all nodes and now none are able to restart. all show me this error Cannot open channel to 3 at election address
    joshblease
    @joshblease
    Hello all! I'm trying to repair a bookkeeper cluster with the auto-recovery tool but it doesn't want to run along side the current process - " Address already in use"
    Looks like a conflict for prometheusStatsHttpPort
    joshblease
    @joshblease
    Right, changed that port and we're running. The auto recovery is attempting to connect to a bookie which has been lost (VM issues), is this expected?
    Enrico Olivelli
    @eolivelli
    @joshblease welcome to this channel, I am from BK community. Can you please move this question to BK slack channel? You can find it on bookkeeper.apache.org
    rajatgangwar
    @rajatgangwar

    [curator][lock-recipe] pre ZK 3.5 (container nodes), curator lock implementation creates persistent parent node and ephemeral-sequential child node. I believe this is done to mitigate herd-effect. But we have a use-case where 99.99% calls are unique, and we need lock just in case 2 duplicate calls come at the same time. Given that we are still stuck with ZK 3.4 and I want to avoid reaper (since it is deprecated), can I implement a lock recipe which just tries to create ephemeral node without any persistent nodes. Since ZK will fail if node already exists, this will ensure only one call (among the duplicate concurrent calls) will go through ?

    Are there any corner cases where it will not work ?
    Since I didn't find any library(recipe) with such implementation I was not sure about it.
    Can someone please tell me if there is any problem with this approach for the use-case where duplicates are very rare, but whenever it happens we need to make sure only one call goes through?

    Ajith Kumar Rajendran
    @AjithKumar-Raj
    Is one zookeeper Ensemble can handle multiple kafka cluster?