What d you mean?

This is appended to kafka-run-class.sh

KAFKA_JMX_OPTS="-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false"

prior to running the below in the shel I run =>  export
KAFKA_HEAP_OPTS="-Xmx1G -Xms1G"

I start kafka like this: /var/lib/kafka-0.8.0-src/bin/kafka-server-start.sh
/var/lib/kafka-0.8.0-src/config/server.properties

What else is there do?  I did not have an issue with kafka 7.  Only 8.

Thanks








On Fri, Jan 31, 2014 at 4:47 AM, Benjamin Black <b...@b3k.us> wrote:

> are you sure the java opts are being set as you expect?
> On Jan 30, 2014 12:41 PM, "David Montgomery" <davidmontgom...@gmail.com>
> wrote:
>
> > Hi,
> >
> > This is a dedicated machine on DO.    But i can say I did not have a
> > problem with kafka 7.
> > I just upgraded the macine to 1gig on digi ocean.  Same error.
> >
> > export KAFKA_HEAP_OPTS="-Xmx1G -Xms1G"
> > root@do-kafka-sf-development-20140130195343:/etc/supervisor/conf.d#
> > /var/lib/kafka-0.8.0-src/bin/kafka-server-start.sh
> > /var/lib/kafka-0.8.0-src/config/server.properties
> > OpenJDK 64-Bit Server VM warning: INFO:
> > os::commit_memory(0x00000000bad30000, 986513408, 0) failed; error='Cannot
> > allocate memory' (errno=12)
> > #
> > # There is insufficient memory for the Java Runtime Environment to
> > continue.
> > # Native memory allocation (malloc) failed to allocate 986513408 bytes
> for
> > committing reserved memory.
> > # An error report file with more information is saved as:
> > # /etc/supervisor/conf.d/hs_err_pid11635.log
> >
> >
> >
> > Below is how I install via chef
> >
> >     version = '0.8.0'
> >     tar -xzf kafka-#{version}-src.tgz
> >     cd kafka-#{version}-src
> >     ./sbt update
> >     ./sbt package
> >     ./sbt assembly-package-dependency
> >     echo 'KAFKA_JMX_OPTS="-Dcom.sun.management.jmxremote=true
> > -Dcom.sun.management.jmxremote.authenticate=false
> > -Dcom.sun.management.jmxremote.ssl=false"' | tee -a
> > /var/lib/kafka-#{version}-src/bin/kafka-run-class.sh
> >     echo 'export JMX_PORT=${JMX_PORT:-9999}' | tee -a
> > /var/lib/kafka-#{version}-src/bin/kafka-server-start.sh
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Fri, Jan 31, 2014 at 4:04 AM, Jay Kreps <jay.kr...@gmail.com> wrote:
> >
> > > I think this may be more a general java thing. Can you try running any
> > java
> > > class with the same command line options you are using for kafka and
> > > confirm that that also doesn't work.
> > >
> > > -Jay
> > >
> > > On Thu, Jan 30, 2014 at 11:23 AM, David Montgomery <
> > > davidmontgom...@gmail.com> wrote:
> > >
> > > > Hi, <%20us...@kafka.apache.org>
> > > >
> > > > Why oh whhy can I nt start kafka 8?  I am on a machine with 512 megs
> of
> > > ram
> > > > on digi ocean.  What does one have to do to get kafka to work?
> > > >
> > > >
> > > >
> > > > root@do-kafka-sf-development-20140130051956: export
> > > > KAFKA_HEAP_OPTS="-Xmx256M -Xms128M
> > > > root@do-kafka-sf-development-20140130051956:/etc/supervisor/conf.d#
> > > > /var/lib/kafka-0.8.0-src/bin/kafka-server-start.sh
> > > > /var/lib/kafka-0.8.0-src/config/server.properties
> > > > OpenJDK 64-Bit Server VM warning: INFO:
> > > > os::commit_memory(0x00000000bad30000, 986513408, 0) failed;
> > error='Cannot
> > > > allocate memory' (errno=12)
> > > > #
> > > > # There is insufficient memory for the Java Runtime Environment to
> > > > continue.
> > > > # Native memory allocation (malloc) failed to allocate 986513408
> bytes
> > > for
> > > > committing reserved memory.
> > > > # An error report file with more information is saved as:
> > > > # /etc/supervisor/conf.d/hs_err_pid17533.log
> > > >
> > > >
> > > > Thanks
> > > >
> > >
> >
>

Reply via email to