Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Stevo Slavić
    @sslavic
    haven't tried it
    I was trying to start jocko cluster by https://github.com/travisjeffery/jocko/tree/master/examples/cluster but it's outdated, PR still in the making travisjeffery/jocko#98 getting serf configuration to work remains to be done, seems there was recent refactoring, and it's not complete
    @JeanMertz are you starting single Jocko instance?
    Jean Mertz
    @JeanMertz
    Yes, and not with the CLI, but straight from the tests. As I mentioned, the Sarama test actually passes, so things are working on the server-side, and also on the Sarama client side, just not the confluent-kafka one.
    Actually, thinking about it, I see that the Sarama test uses the v0.10 API version, Kafka already went to v0.11, and since recently v1.0, so that might actually be it, I bet if I put the Sarama version on anything higher than 0.10, it will break as well.
    Stevo Slavić
    @sslavic
    well, by the docs, Jocko is targeting 0.10 compatibility for now
    Jean Mertz
    @JeanMertz
    Ah right, I missed that documentation, I see it mentioned now at travisjeffery/jocko#1
    Stevo Slavić
    @sslavic
    I guess rationale is that it has new clients, streaming are all supported in 0.10 - once all is working with 0.10, supporting newer protocol would be possible
    Jean Mertz
    @JeanMertz

    Hm yeah. There is this: https://github.com/edenhill/librdkafka/wiki/Broker-version-compatibility#detailed-description

    But it looks like that isn't working as expected either, I still get a Connection closed when setting the proper API version (0.10.0.0).

    Stevo Slavić
    @sslavic
    I'd debug server
    monetashi-io
    @monetashi-io
    Hai Travis and everybody, this is a very promising project! Is jocko ready to be used in a production environment? Anybody running this under any kind of load, and what are your experiences?
    yctn
    @yctn
    anyone already using this?
    Jack Tuck
    @jacktuck
    soon!
    replication and consumer groups are WIP if i understand correctly :)
    Stevo Slavić
    @sslavic
    @travisjeffery would there be difference at all if Jocko targeted Kafka 2.0 (without Scala high-level + simple consumer APIs, and sync+async producer) instead of 0.10 protocol compatibility?
    markfarnan
    @markfarnan
    Hello: I'm sure this has been asked a dozen times, (I can't see any real answers to it), BUT, any feel for how close this is to Production-Ready ? I need a nice, compact, FAST, Single node queue, and Kafka compatibility is great !. (Eventually will use it for Multi Server, / data center but first goal is single machine deployments.
    stick me in the 'despise zookeeper' bucket for why looking at this, And all our new stuff is in GO
    markfarnan
    @markfarnan
    ANyone even here ?
    Ilia Choly
    @icholy
    It's not production ready
    Daniel Nishimura
    @dnishimura
    Been keeping an eye on this a while too. Time to find a successor or fork it?
    Ilia Choly
    @icholy
    redis streams are pretty dope
    I've developed an in-house solution for my use-case using leveldb
    Daniel Nishimura
    @dnishimura
    been hearing a lot about redis streams recently. I should look into.
    loved using redis at my prev startup. It just works.
    yctn
    @yctn
    @travisjeffery maby you could provide us an update on this project
    jmwilkinson
    @jmwilkinson
    It looks like this project is mostly dead/unmaintained?