2018-07-29 18:58:08 UTC - Poule: @jia zhai I need to fix it in DC/OS config or
in PulsarGroups.json or elsewhere?
----
2018-07-29 22:11:51 UTC - Poule: ```
root@zookeeper ~/apache-pulsar-2.0.1-incubating # bin/pulsar zookeeper
Exception in thread "main" java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at com.ea.agentloader.AgentLoader$1.loadAgent(AgentLoader.java:244)
at com.ea.agentloader.AgentLoader.loadAgent(AgentLoader.java:77)
at com.ea.agentloader.AgentLoader.loadAgentClass(AgentLoader.java:148)
at com.ea.agentloader.AgentLoader.loadAgentClass(AgentLoader.java:102)
at
org.apache.pulsar.zookeeper.ZooKeeperStarter.start(ZooKeeperStarter.java:46)
at
org.apache.pulsar.zookeeper.ZooKeeperStarter.main(ZooKeeperStarter.java:38)
Caused by: java.lang.reflect.InvocationTargetException
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at com.ea.agentloader.AgentLoader$1.loadAgent(AgentLoader.java:240)
... 5 more
Caused by: java.lang.RuntimeException: java.io.IOException: Can not attach to
current VM
at
com.ea.agentloader.AgentLoaderHotSpot.getVirtualMachine(AgentLoaderHotSpot.java:90)
at
com.ea.agentloader.AgentLoaderHotSpot.loadAgent(AgentLoaderHotSpot.java:56)
... 10 more
Caused by: java.io.IOException: Can not attach to current VM
at
jdk.attach/sun.tools.attach.HotSpotVirtualMachine.<init>(HotSpotVirtualMachine.java:75)
at
jdk.attach/sun.tools.attach.VirtualMachineImpl.<init>(VirtualMachineImpl.java:60)
at
jdk.attach/sun.tools.attach.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:58)
at
jdk.attach/com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:207)
at
com.ea.agentloader.AgentLoaderHotSpot.getVirtualMachine(AgentLoaderHotSpot.java:86)
```
----
2018-07-29 22:30:02 UTC - Poule: trying to setup Pulsar without DC/OS I get
this ^^
----
2018-07-29 22:31:44 UTC - Ali Ahmed: what is the jdk version ?
----
2018-07-29 22:34:40 UTC - Poule: ```
root@zookeeper ~/apache-pulsar-2.0.1-incubating # javac -version
javac 10.0.1
root@zookeeper ~/apache-pulsar-2.0.1-incubating # java -version
openjdk version "10.0.1" 2018-04-17
OpenJDK Runtime Environment (build 10.0.1+10-Ubuntu-3ubuntu1)
OpenJDK 64-Bit Server VM (build 10.0.1+10-Ubuntu-3ubuntu1, mixed mode)
```
----
2018-07-29 22:35:23 UTC - Ali Ahmed: we currently only support jdk 8
----
2018-07-29 22:36:12 UTC - Poule: docs says Java 8 or higher :scream:
----
2018-07-29 22:37:09 UTC - Matteo Merli: good point. we actually wrote that
before java9 was available. we need to fix it
----
2018-07-30 01:03:07 UTC - jia zhai: @Poule Is it OK running on java 8 or 9?
----
2018-07-30 01:07:19 UTC - Poule: @jia zhai
1) my first problem of DC/OS + DigitalOcean I don't know how to fix it
2) my second problem of running Pulsar without DC/OS was fixed by Java8 yes
----
2018-07-30 01:41:18 UTC - jia zhai: Hi @Poule Searched some similar error:
<https://github.com/mesosphere/dcos-kafka-service/issues/259>
<https://stackoverflow.com/questions/45391980/error-installing-flink-in-dcos>
Seems most of them are fix by adding agent hostname to the /etc/hosts
----
2018-07-30 02:19:01 UTC - Poule: @jia zhai nice, thanks. so it actually reads
the file or something
----
2018-07-30 02:21:29 UTC - jia zhai: :+1: @Poule Yes, /etc/hosts is some kind of
a local DNS
----
2018-07-30 02:23:35 UTC - Poule: yes I know but "digitalocean-dcos-agent-01"
was pinging correctly so I assumed the DNS was ok
----
2018-07-30 02:23:58 UTC - Poule: it actually needs it in the file
----
2018-07-30 02:24:09 UTC - Poule: for some reason
----
2018-07-30 02:32:06 UTC - Poule: if I benchmark with `bin/pulsar-perf produce
-r 100000 -m 10000000 <persistent://public/default/perf>`
----
2018-07-30 02:32:34 UTC - Poule: i should see the topic with `bin/pulsar-admin
topics list public/default`right?
----
2018-07-30 02:49:21 UTC - Matteo Merli: yes, and you should also see the stats
with `bin/pulsar-admin topics stats perf`
----
2018-07-30 02:49:49 UTC - Matteo Merli: (`perf` is equivalent to
`<persistent://public/default/perf>` )
----
2018-07-30 03:03:07 UTC - Poule: if it's not in the topics list what happened?
----
2018-07-30 03:05:48 UTC - Poule: they appear for some time then they disappear
----
2018-07-30 03:14:24 UTC - Poule: they disappear after approx 90 seconds, is
there something that run every 90 seconds?
----
2018-07-30 04:02:27 UTC - Poule: they disappear also from `bin/pulsar-admin
broker-stats topics -i` after the same time
----
2018-07-30 04:06:17 UTC - Poule: also I can't delete
```
root@broker ~/apache-pulsar-2.0.1-incubating #bin/pulsar-admin topics list
public/pulsar-cluster-1/yoshi
<persistent://public/pulsar-cluster-1/yoshi/perf55>
<persistent://public/pulsar-cluster-1/yoshi/test>
<persistent://public/pulsar-cluster-1/yoshi/perf>
root@broker ~/apache-pulsar-2.0.1-incubating # bin/pulsar-admin topics delete
<persistent://public/pulsar-cluster-1/yoshi/perf>
06:03:50.346 [jersey-client-async-executor-0] WARN
org.apache.pulsar.client.admin.internal.BaseResource -
[<http://localhost:8080/admin/persistent/public/pulsar-cluster-1/yoshi/perf?force=false>]
Failed to perform http delete request:
javax.ws.rs.InternalServerErrorException: HTTP 500 Request failed.
HTTP 500 Request failed.
Reason: Some error occourred on the server
```
----
2018-07-30 04:50:54 UTC - Matteo Merli: @Poule yes, when topics are not used
and there are no subscriptions (or retention being configured), they will be
automatically deleted.
----
2018-07-30 04:51:46 UTC - Matteo Merli: The auto deletion can also be disabled
in broker.conf
----
2018-07-30 04:55:50 UTC - Poule: I got confused by this : ```By default, when a
Pulsar message arrives at a broker it will be stored until it has been
acknowledged by a consumer, at which point it will be deleted.```
`persistently store all unacknowledged messages in a backlog.`
----
2018-07-30 04:56:52 UTC - Matteo Merli: In your cases if there are no
subscriptions, and retention is disabled, the data can be deleted immediately
----
2018-07-30 04:57:25 UTC - Poule: ok
----
2018-07-30 05:02:53 UTC - Matteo Merli: Either subscriptions or time retention
are ways to ensure the data (and the topic) will not be dropped.
If you have both, you can also rollback subscriptions to an earlier point in
time
----
2018-07-30 05:24:59 UTC - penghui li: @penghui li has joined the channel
----
2018-07-30 06:24:58 UTC - Vasily Yanov: Hi Trying to start pulsar 1.22.1 in
standalone mode but got:
```
root@dev-exvv-01 /opt/pulsar # java -version
openjdk version "1.8.0_171"
OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-0ubuntu0.16.04.1-b11)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)
root@dev-exvv-01 /opt/pulsar # bin/pulsar standalone
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/pulsar/client/admin/PulsarAdminException
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
at java.lang.Class.getMethod0(Class.java:3018)
```
----
2018-07-30 06:25:04 UTC - Vasily Yanov: how it could be fixed?
----
