Slack digest for #general - 2018-05-07

[Apache Pulsar Slack <ap...@gmail.com>]

2018-05-06 16:21:15 UTC - William: @Ali Ahmed Thanks! Has the community converged on any best practices for these kinds of use cases?
----
2018-05-06 19:08:31 UTC - Ali Ahmed: there is a lot variety , it really depends how you want to isolate the cluster,  for some people they want to  isolate brokers for tenants with specific certificates , others may want isolate read , write , or replicated paths , not simple to capture best practices but something the community can try.
----
2018-05-06 22:25:08 UTC - Josh West: @Josh West has joined the channel
----
2018-05-07 02:14:55 UTC - Josh West: Hi folks.  Is there any word or progress on the possibility of an official Golang client for Pulsar?
----
2018-05-07 02:17:31 UTC - Matteo Merli: Hi Josh, some people were working on a pure Go client. I’ve started work on Cgo based library that leverages the C++ pulsar client library. I’ll post details here in the coming days, to collect feedback on the Go ergonomics of the API
----
2018-05-07 02:18:17 UTC - Josh West: very cool @Matteo Merli
----
2018-05-07 02:18:18 UTC - Josh West: thanks
----
2018-05-07 02:18:29 UTC - Josh West: i'm doing a comparison of various messaging solutions at the moment
----
2018-05-07 02:18:45 UTC - Josh West: the candidates are Pulsar, NATS, RabbitMQ, VerneMQ, Kafka
----
2018-05-07 02:19:04 UTC - Josh West: one of the strong standouts as an issue with Pulsar (despite the rest of its strengths) is no good Golang client
----
2018-05-07 02:19:08 UTC - Josh West: looking forward to your work!
----
2018-05-07 02:21:19 UTC - Matteo Merli: :+1: We are well aware of the need for Go client. It will be included in next release 2.1 planned for early Jun.
+1 : Sijie Guo, Ali Ahmed
----
2018-05-07 02:22:49 UTC - Josh West: nice!
----
2018-05-07 08:31:53 UTC - Vasily Yanov: Hi! Trying to continue with our stresstests. Now Pulsar is dead with a lot of errors in logs:
```
2018-05-07 08:25:35,663 - WARN  [bookkeeper-ml-workers-31-1:ServerCnx@650] - [/1.9.81.1:55193][<persistent://server-ali-t2-1525678483902/prod-pulsar-cluster-1/session_queue/f7115f40-0f3e-4a74-bb47-3>
java.util.concurrent.CompletionException: org.apache.pulsar.broker.service.BrokerServiceException: Connection was closed while the opening the cursor
```
----
2018-05-07 08:32:25 UTC - Vasily Yanov: and after that
```
2018-05-07 08:25:55,064 - ERROR [pulsar-web-61-16:PulsarWebResource@388] - [null] Failed to validate namespace bundle server-ali-t2-1525678483902/prod-pulsar-cluster-1/session_queue/0x7ffffff8_0x8aa
java.lang.IllegalArgumentException: Invalid upper boundary for bundle
```
----
2018-05-07 08:34:18 UTC - Vasily Yanov: any assumptions?
----
2018-05-07 08:51:49 UTC - jia zhai: the bundle range is strange, when “0x8aa” is first appearance?
----
2018-05-07 08:59:06 UTC - Vasily Yanov: what do you mean "first appearance"? it appeared after bookkeeper warnings "Connection was closed while the opening the cursor". See timestamps for two messages: they differ for 20 seconds
----