You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Florian Leibert <fl...@leibert.de> on 2011/12/09 17:45:31 UTC

Multiple brokers on the same host

Hi -
trying to run multiple brokers on one host for testing I ran into issues of
port 9999 already being used. I created a new properties file for each
broker and changed the regular broker port to listen on a different port
(btw - if using ZK for service registration / discover, is there any reason
as to why one would have to use a fixed port?) - however for some reason
RMI is requiring port 9999 - what's that used for? Is there a properties
flag that changes this?

Thanks
Flo

Re: Multiple brokers on the same host

Posted by Florian Leibert <fl...@leibert.de>.
Never mind - this was my negligence - sorry for the spam.

On Fri, Dec 9, 2011 at 8:57 AM, Florian Leibert <fl...@leibert.de> wrote:

> Though now I do get a new BindException:
> Exception in thread "kafka-acceptor" java.net.BindException: Address
> already in use
> at sun.nio.ch.Net.bind(Native Method)
>  at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>  at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52)
> at kafka.network.Acceptor.run(SocketServer.scala:125)
>  at java.lang.Thread.run(Thread.java:680)
>
>
> On Fri, Dec 9, 2011 at 8:53 AM, Florian Leibert <fl...@leibert.de> wrote:
>
>> Thanks - I forgot that there's JMX being used... makes all sense now!
>>
>>
>> On Fri, Dec 9, 2011 at 8:50 AM, David Ormsbee <da...@datadoghq.com> wrote:
>>
>>> You can override that with the JMX_PORT environment variable. So
>>> something
>>> like:
>>>
>>> env JMX_PORT=10000 [server start script]
>>>
>>> Dave
>>>
>>> On Fri, Dec 9, 2011 at 11:45 AM, Florian Leibert <fl...@leibert.de> wrote:
>>>
>>> > Hi -
>>> > trying to run multiple brokers on one host for testing I ran into
>>> issues of
>>> > port 9999 already being used. I created a new properties file for each
>>> > broker and changed the regular broker port to listen on a different
>>> port
>>> > (btw - if using ZK for service registration / discover, is there any
>>> reason
>>> > as to why one would have to use a fixed port?) - however for some
>>> reason
>>> > RMI is requiring port 9999 - what's that used for? Is there a
>>> properties
>>> > flag that changes this?
>>> >
>>> > Thanks
>>> > Flo
>>> >
>>>
>>
>>
>>
>> --
>> Best regards,
>>
>> Florian
>> http://twitter.com/flo <http://twitter.com/floleibert>
>> http://flori.posterous.com/
>>
>>
>
>
> --
> Best regards,
>
> Florian
> http://twitter.com/flo <http://twitter.com/floleibert>
> http://flori.posterous.com/
>
>


-- 
Best regards,

Florian
http://twitter.com/flo <http://twitter.com/floleibert>
http://flori.posterous.com/

Re: Multiple brokers on the same host

Posted by Florian Leibert <fl...@leibert.de>.
Though now I do get a new BindException:
Exception in thread "kafka-acceptor" java.net.BindException: Address
already in use
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52)
at kafka.network.Acceptor.run(SocketServer.scala:125)
at java.lang.Thread.run(Thread.java:680)


On Fri, Dec 9, 2011 at 8:53 AM, Florian Leibert <fl...@leibert.de> wrote:

> Thanks - I forgot that there's JMX being used... makes all sense now!
>
>
> On Fri, Dec 9, 2011 at 8:50 AM, David Ormsbee <da...@datadoghq.com> wrote:
>
>> You can override that with the JMX_PORT environment variable. So something
>> like:
>>
>> env JMX_PORT=10000 [server start script]
>>
>> Dave
>>
>> On Fri, Dec 9, 2011 at 11:45 AM, Florian Leibert <fl...@leibert.de> wrote:
>>
>> > Hi -
>> > trying to run multiple brokers on one host for testing I ran into
>> issues of
>> > port 9999 already being used. I created a new properties file for each
>> > broker and changed the regular broker port to listen on a different port
>> > (btw - if using ZK for service registration / discover, is there any
>> reason
>> > as to why one would have to use a fixed port?) - however for some reason
>> > RMI is requiring port 9999 - what's that used for? Is there a properties
>> > flag that changes this?
>> >
>> > Thanks
>> > Flo
>> >
>>
>
>
>
> --
> Best regards,
>
> Florian
> http://twitter.com/flo <http://twitter.com/floleibert>
> http://flori.posterous.com/
>
>


-- 
Best regards,

Florian
http://twitter.com/flo <http://twitter.com/floleibert>
http://flori.posterous.com/

Re: Multiple brokers on the same host

Posted by Florian Leibert <fl...@leibert.de>.
Thanks - I forgot that there's JMX being used... makes all sense now!

On Fri, Dec 9, 2011 at 8:50 AM, David Ormsbee <da...@datadoghq.com> wrote:

> You can override that with the JMX_PORT environment variable. So something
> like:
>
> env JMX_PORT=10000 [server start script]
>
> Dave
>
> On Fri, Dec 9, 2011 at 11:45 AM, Florian Leibert <fl...@leibert.de> wrote:
>
> > Hi -
> > trying to run multiple brokers on one host for testing I ran into issues
> of
> > port 9999 already being used. I created a new properties file for each
> > broker and changed the regular broker port to listen on a different port
> > (btw - if using ZK for service registration / discover, is there any
> reason
> > as to why one would have to use a fixed port?) - however for some reason
> > RMI is requiring port 9999 - what's that used for? Is there a properties
> > flag that changes this?
> >
> > Thanks
> > Flo
> >
>



-- 
Best regards,

Florian
http://twitter.com/flo <http://twitter.com/floleibert>
http://flori.posterous.com/

Re: Multiple brokers on the same host

Posted by David Ormsbee <da...@datadoghq.com>.
You can override that with the JMX_PORT environment variable. So something
like:

env JMX_PORT=10000 [server start script]

Dave

On Fri, Dec 9, 2011 at 11:45 AM, Florian Leibert <fl...@leibert.de> wrote:

> Hi -
> trying to run multiple brokers on one host for testing I ran into issues of
> port 9999 already being used. I created a new properties file for each
> broker and changed the regular broker port to listen on a different port
> (btw - if using ZK for service registration / discover, is there any reason
> as to why one would have to use a fixed port?) - however for some reason
> RMI is requiring port 9999 - what's that used for? Is there a properties
> flag that changes this?
>
> Thanks
> Flo
>