params undefined when starting client about seneca-kafka-transport HOT 7 OPEN

Hi,
Can you confirm that the topics are created in kafka - you will need a 'request' and a 'response' each with 3 partitions. setConfig.js does not create the topics in Kafka, it just initializes a configuration block in zookeeper. Apologies for the confusion will update the documentation to make that clearer!

from seneca-kafka-transport.

Thank you for the reply!
For this particular case I cannot confirm topics creation. Also there were problems in kafka itself when running it under windows.

On clean Linux installation I could run the tests successfully. (with 2 topics x 3 partitions each).
in my setup I run 1 client and 3 servers each of them getting messages from own partition.

However after several restarts of server.js processes I started to get this error again.
Looks like there is some problem in leader selection.

Now it is impossible to run the tests again without full cleanup of kafka and zookeeper logs.

Thanks,
Roman

from seneca-kafka-transport.

Finally I found the problem.
There are no more slots available. i.e. if I break service execution in debugger - slot remains occupied and does not let new connections.
its in microbial and config.

what would be the best approach to free slots if service crashed?

Also I think it would be nice to display a friendly message that there are no more available slots.

from seneca-kafka-transport.

Ah OK - thanks for getting back. Now I understand. There is a process on exit and SIGINT handler that would normally catch this and freeup the slot on normal or Ctrl-C process termination. However when using the debugger this will most likely not get called :)
For testing / debugging there there is a script in the test folder called deregister.js. If you run this it will free up all slots in zookeeper.

Will update the docs to explain this. Really appreciate the feedback!

from seneca-kafka-transport.

Hi,

I have been experiencing the same issue; initially after starting client.js a few times, subsequently on multiple server.js restarts.
I had configured 'request' & 'response' topics each with 3 partitions - tested operation with Kafka/ZK instances running locally (OSX Mavericks) and also on a clean debian Linux distro VM.
Also tried using deregister.js to deallocate zk slots, but the same error is generated.

from seneca-kafka-transport.

@cdromka @Bazm0 adding you as contribs
@pelger any pointers for a fix?

from seneca-kafka-transport.

@cdromka @Bazm0
Were you able to resolve this problem?

@pelger
My set-up, as per eolas-tracer, isn't exactly as per seneca-kafka-transport, but I think it emulates it closely. I'm experiencing these problems described above too and microbial/kafkaesque/zookeeper interaction is really opaque. I tried running your suggested deregister.js script, changing the namespace from seneca to my own, but that doesn't appear to resolve.

Thanks for any input you can offer.
Colum

from seneca-kafka-transport.