Hi Pradyumna,
It's possible. Here are some points:
1. kafka.Kafka is the class you want to run.
2. As the parameter, pass the path to your server.properties, i.e. the config
file.
3. Point to the logger config as the VM properties:
-Dlog4j.configuration=file:/path/to/log4j.properties.
4. You nee
Hi,
You can also import the Kafka project as a Gradle project in IntelliJ,
and then create an Application Run Configuration to run/debug it.
In your run configuration, set the module classpath to
kafka.core.main, the main class to kafka.Kafka, and the program
arguments to one of the server.propert
I've found one approach that works. Posting it here in case someone else
needs it.
If there is a simpler method, do let me know.
Use "./gradlew clean releaseTarGz -x test" to build a tarball with my
changes
Take the generated tarball in core/build/distributions, expand it and run
it.
Set KAFKA_
Thank you.
Looks like I too accidentally discovered this approach minutes before your
reply.
I wasn't aware of the DEBUG_SUSPEND_FLAG though. It is useful.
Regards
Pradyumna
Hi Pradyumna,
Yes, you can do this. What I tend to do is to start my broker from a terminal
window with the
DEBUG_SUSPEND_FLAG and KAFKA_DEBUG environment variables set. This means the
broker
suspends as it starts and waits for a connection from a debugger. Then I attach
IntelliJ to the
running
