Slack digest for #dev - 2020-06-18

[Apache Pulsar Slack]

2020-06-17 15:07:12 UTC - Chris Herzog: @Chris Herzog has joined the channel

2020-06-17 16:17:58 UTC - Leonard Ge: @Leonard Ge has joined the channel

2020-06-17 17:59:36 UTC - Pedro Cardoso: @Sijie Guo Is the blog post out? I'm 
also very interested in hearing Pulsar's version.

2020-06-17 18:05:35 UTC - Sijie Guo: @Pedro Cardoso not yet. We have the draft. 
It is under reviews by bunch of people in the community. We will probably 
publish in 1~2 weeks or so.

2020-06-17 18:07:38 UTC - Pedro Cardoso: Could you share it? Even if a draft, 
it would still be useful as right now I'm benchmarking kafka (considering 
pulsar as a future improvement) and have some wierd results I would like to 
confirm.

2020-06-17 18:07:50 UTC - Pedro Cardoso: If you have data to backup the claims 
it would be even better.

2020-06-17 18:10:33 UTC - Sijie Guo: @Pedro Cardoso It is more on the 
clarifications on statements. Are you looking for benchmark results?

2020-06-17 18:10:57 UTC - Pedro Cardoso: As a start yes. I'm writing a message 
in the main chat. Give me a couple minutes.

2020-06-17 18:13:03 UTC - Sijie Guo: If you have performance issues, you can 
post the questions and we can help with them. For benchmark results, I think 
Splunk is going to publish their results soon. /cc @Karthik Ramasamy

2020-06-17 18:13:15 UTC - Pedro Cardoso: Thank you so much!

2020-06-17 18:18:13 UTC - Pedro Cardoso: Hello,
Does anyone have benchmarks results comparing Kafka and Pulsar they could share?

Context:
In my company we are looking for a messaging layer of what will be a mission 
critical, millisecond streaming engine and performing Kafka benchmarks to 
understand its performance for our use-case (max latency <100ms @ 5k TPS, 
with 99.999 SLAs, @ 99.95 SLA is <8 ms)
Our benchmark is very simple, a single producer & consumer. We are sending 
a 2KB (generated once) bytebuffer payload, sending that through the producer 
and consuming (no custom logic, just an ack) it.
The setup is a 3 node cluster in AWS all in different availability zones (we 
have tried Kubernetes, regular VMs even AWS's managed service)
Replication factor of 3, 64 partitions, maximum ack level (processing and 
replica broker acks) with random partitioning.
We use Zing's pauseless GC to reduce GC-induced latencies and SSDs to make sure 
we are not I/O bound but still have behaviour we can not account for.

What we are seeing are a few latency spikes always in the order of 200ms which 
are over our SLAs:
Producer: 

Consumer: 


In tabular form the latencies per percentile look something like:
|  |   0   |   25  |   50  |   75  |   90  |   95  |   99  |  99.9 |  
99.99 |  99.999 |   100   |
|::|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:--:|:---:|:---:|
| producer | 1 |  1.83 | 2.274 | 3.054 | 3.872 | 4.633 | 6.588 |  9.72 | 
45.353 | 191.029 | 214.186 |
| consumer | 1.059 | 1.683 | 2.255 | 3.092 | 3.966 | 4.695 | 6.623 | 9.871 | 
117.38 | 199.024 | 214.254 |

(Sorry... slack does not support markdown tables)

Has anyone seem this "spiky" type of behavior in Kafka and more pertinent in 
this chat, what about in Pulsar? It does not seem to be GC (we use zing and 
confirm <1 millisecond gc events with a stable heap, 3GB statically 
allocated via JVM options), CPU or Memory (we are over-provisioning machines, 
m5ad.2x large to be exact), Disk (300 GB SSDs + 20 GB EBS) or Network (10 Gbit 
connection)

2020-06-17 19:06:19 UTC - Vijay Bhore: @Vijay Bhore has joined the channel

2020-06-17 19:18:37 UTC - David Kjerrumgaard: 


2020-06-17 19:19:06 UTC - David Kjerrumgaard: And you can run your own 
benchmark tests using the framework 


2020-06-17 19:24:51 UTC - Andrew: @Andrew has joined the channel

2020-06-17 20:02:14 UTC - Pedro Cardoso: Thank you David! I may end up running 
the benchmarks adapted to my use-case and compare both technologies 
:slightly_smiling_face:
crossed_fingers : David Kjerrumgaard

2020-06-18 05:01:31 UTC - Amit Pal: 1. Can you verify Network is not the 
culprit here? Generally, tcp retransmission / packet loss are reasons for such 
latencies ... I believe IO wouldn't be saturated here
2. Can you look at pulsar broker metrics? Those will tell you the real picture, 
if network at all is an issue.
3. Use a mix of sync/async replication on msg producer (depends on how much 
durability you want)

2020-06-18 07:15:04 UTC - Patrik Kleindl: Just a sidenote, in this test Kafka 
was intentionally configured against best practices to mirror what Pulsar does. 
The performance of Pulsar i

Re: [VOTE] Pulsar Client Go Release 0.1.1 Candidate 1

[ran leon]

+1 (non-binding)

Thanks
Leon

On 2020/06/12 09:41:06, xiaolong ran  wrote: 
> Hi everyone,
> 
> Please review and vote on the release candidate #1 for the version 0.1.1, as 
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> 
> This is the first release candidate for Apache Pulsar Go client, version 
> 0.1.1.
> 
> It fixes the following issues:
> https://github.com/apache/pulsar-client-go/milestone/2?closed=1 
> 
> 
> Pulsar Client Go's KEYS file contains PGP keys we used to sign this release:
> 
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS 
> 
> 
> Please download these packages and review this release candidate:
> 
> - Download the source package (verify shasum, and asc) and follow the
> README.md to build and run the pulsar-client-go.
> 
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval, with at least 3 PMC affirmative votes.
> 
> Source file:
> 
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.1.1-candidate-1/apache-pulsar-client-go-0.1.1-src.tar.gz
>  
> 
> 
> The tag to be voted upon:
> v0.1.1-candidate-1
> https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1-candidate-1 
> 
> 
> SHA-512 checksums:
> 2fed052f49364ccadbf912b360b4ce62ae63540d99b2d497eb8947808eceb8cea058e66f3968919c5f1b53937c3f5155a81b87b6160ea6a84309899481aaffa4
>   apache-pulsar-client-go-0.1.1-src.tar.gz

[ANNOUNCE] Apache Pulsar 2.6.0 released

[PengHui Li]

The Apache Pulsar team is proud to announce Apache Pulsar version 2.6.0.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management
for
subscribers, and cross-datacenter replication.

For Pulsar release details and downloads, visit:

https://pulsar.apache.org/download

Release Notes are at:
http://pulsar.apache.org/release-notes

We would like to thank the contributors that made the release possible.

Regards,

The Pulsar Team

[GitHub] [pulsar-manager] eolivelli opened a new pull request #303: Upgrade HerdDB to 0.16, Pulsar Client to 2.5.2, add demo config for diskless-cluster mode

[GitBox]

eolivelli opened a new pull request #303:
URL: https://github.com/apache/pulsar-manager/pull/303


   ### Motivation
   
   Since HerdDB 0.16 you can store all of the data on BookKeeper, this is 
called "diskless-cluster" mode.
   So you will be able to run PulsarManager + HerdDB on a stateless pod, all of 
the data will be stored on the same BK+ZK cluster as your Pulsar installation. 
   
   ### Modifications
   
   - Upgrade HerdDB to 0.16.1.
   - Upgrade Apache Pulsar Admin Client to 2.5.2 (that officially supports BK 
4.10)
   - Use pulsar-client-admin-original instead of pulsar-client-admin, because 
pulsar-client-admin contains a shaded version of CirceChecksum library from BK 
that is not compatibile with BK 4.10, needed by HerdDB in order to run in 
diskless-cluster  mode.
   - Configure gradle to put application.properties inside pulsar-manager.tar, 
this way it is super easy to change the configuration of pulsar-manager backend 
without recompiling the package (no need to use Gradle for System administrator)
   - Add an example JDBC URI to boot HerdDB in diskless-cluster mode
   
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the `./gradlew build` checks.
   
   
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Pulsar Client Go Release 0.1.1 Candidate 1

[lan.liang]

+1 nb








- lan.liang
On 6/18/2020 17:20，ran leon wrote：
+1 (non-binding)

Thanks
Leon

On 2020/06/12 09:41:06, xiaolong ran  wrote:
Hi everyone,

Please review and vote on the release candidate #1 for the version 0.1.1, as 
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

This is the first release candidate for Apache Pulsar Go client, version 0.1.1.

It fixes the following issues:
https://github.com/apache/pulsar-client-go/milestone/2?closed=1 


Pulsar Client Go's KEYS file contains PGP keys we used to sign this release:

https://dist.apache.org/repos/dist/dev/pulsar/KEYS 


Please download these packages and review this release candidate:

- Download the source package (verify shasum, and asc) and follow the
README.md to build and run the pulsar-client-go.

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.

Source file:

https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.1.1-candidate-1/apache-pulsar-client-go-0.1.1-src.tar.gz
 


The tag to be voted upon:
v0.1.1-candidate-1
https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1-candidate-1 


SHA-512 checksums:
2fed052f49364ccadbf912b360b4ce62ae63540d99b2d497eb8947808eceb8cea058e66f3968919c5f1b53937c3f5155a81b87b6160ea6a84309899481aaffa4
  apache-pulsar-client-go-0.1.1-src.tar.gz

[GitHub] [pulsar-manager] eolivelli commented on pull request #303: Upgrade HerdDB to 0.16, Pulsar Client to 2.5.2, add demo config for diskless-cluster mode

[GitBox]

eolivelli commented on pull request #303:
URL: https://github.com/apache/pulsar-manager/pull/303#issuecomment-646012196


   @tuteng @sijie  PTAL



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSS] PIP-67: Contribute Pulsarctl to Apache Pulsar

[Yong Zhang]

It seems that there are no objections to accepting this repo.

What should I do in the next step? Should I open a vote in a separate email?

Thanks

---
On Mon, 15 Jun 2020 at 14:30, Guangning E  wrote:

> Great job, +1, Thanks Yong and Xiaolong.
>
> anonymitaet _  于2020年6月15日周一 上午9:56写道：
>
> > Thanks Yong for this great job, +1
> >
> > On 2020/6/15, 09:34, "PengHui Li"  wrote:
> >
> > +1
> > On Jun 15, 2020, 9:24 AM +0800, xiaolong ran <
> ranxiaolong...@gmail.com>,
> > wrote:
> > > Thanks Yong Zhang work for this, LGTM+1
> > >
> > > --
> > > Thanks
> > > Xiaolong Ran
> > >
> > > > 在 2020年6月12日，上午11:38，Yong Zhang  写道：
> > > >
> > > > Hi all,
> > > >
> > > > We have developed a new tool Pulsarctl for managing Pulsar
> > resources. It’s
> > > > written in Golang
> > > > and is an alternative tool of pulsar-admin. We’d like to
> > contribute the
> > > > project back to the Pulsar
> > > > community.
> > > >
> > > > ## Motivation
> > > >
> > > > Pulsarctl is an alternative tool of pulsar-admin, used to manage
> > resources
> > > > in Apache Pulsar.
> > > > Pulsarctl is written in Go and based on Pulsar REST API. It
> > provides Go
> > > > developers with API
> > > > interface and user-friendly commands, making it easier to
> interact
> > with
> > > > Pulsar brokers.
> > > >
> > > > Compared with pulsar-admin, Pulsarctl is more user-friendly.
> > Pulsarctl
> > > > requires fewer dependencies
> > > > to use commands and provides more comprehensive description and
> > usage for
> > > > commands.
> > > > With Pulsarctl, users can find and resolve issues faster when
> > errors occur.
> > > >
> > > > ## Features
> > > >
> > > > Pulsarctl not only integrates the Pulsar commands and BookKeeper
> > commands
> > > > but also
> > > > provides some useful tools like output format and context
> > management.
> > > >
> > > >
> > > > ### Pulsar operations
> > > >
> > > > For Pulsar operations, Pulsarctl integrates almost all the
> > commands of
> > > > pulsar-admin, including
> > > > but not limited to the following operations:
> > > >
> > > > - broker operations
> > > > - cluster operations
> > > > - tenant operations
> > > > - namespace operations
> > > > - topic operations
> > > > - function operations
> > > > - sink operations
> > > > - source operations
> > > >
> > > > Also, Pulsarctl supports the JWT(JSON Web Token) authentication
> > and TLS
> > > > authentication.
> > > >
> > > > The following are command flags of Pulsarctl. You can use
> > `--auth-params`
> > > > to specify the auth
> > > > params configured in pulsar-client. Or you can just specify
> > `--token` to
> > > > use that token to connect the broker.
> > > >
> > > > ```
> > > > Common flags:
> > > > -s, --admin-service-url string The admin web service url that
> > > > pulsarctl connects to. (default "http://localhost:8080";)
> > > > --auth-params string Authentication parameters are used to
> > > > configure the public and private key files required by tls
> > > > For example:
> > > > "tlsCertFile:val1,tlsKeyFile:val2"
> > > > -C, --color string toggle colorized logs
> > > > (true,false,fabulous) (default "true")
> > > > -h, --help help for this command
> > > > --tls-allow-insecure Allow TLS insecure connection
> > > > --tls-trust-cert-path string Allow TLS trust cert file path
> > > > --token string Using the token to authentication
> > > > --token-file string Using the token file to authentication
> > > > -v, --verbose int set log level, use 0 to silence, 4 for
> > > > debugging (default 3)
> > > > ```
> > > >
> > > > ### BookKeeper operations
> > > >
> > > > For BookKeeper operations, Pulsarctl integrates the commands
> > listed in the
> > > > [REST API](https://bookkeeper.apache.org/docs/4.10.0/admin/http/
> )
> > > >
> > > > - auto-recovery operations
> > > > - bookie operations
> > > > - bookies operations
> > > > - ledger operations
> > > >
> > > >
> > > > ### Save your configuration in the different contexts
> > > >
> > > > Pulsarctl provides a context command which lets you manage your
> > Pulsar
> > > > cluster easier.
> > > > The ‘context’ can save the different configurations of your
> Pulsar
> > cluster.
> > > > And you can easily
> > > > change to another cluster by the command `pulsarctl context use`.
> > For more
> > > > details please
> > > > refer to
> > > >
> >
> https://github.com/streamnative/pulsarctl/blob/master/docs/en/how-to-use-context.md
> > > >
> > > >
> > > > ### Get different formats of the output
> > > >
> > > > Pulsarctl provides an output flag `--output` to make the output
> > transform
> > > >

[GitHub] [pulsar-manager] lzhpo commented on issue #283: Pulsar Manager keeps saying "This environment is error. Please check it"

[GitBox]

lzhpo commented on issue #283:
URL: https://github.com/apache/pulsar-manager/issues/283#issuecomment-646424406


   I also encountered this problem. How did you solve it?
   My port is 8080, my curl-v http://127.0.0.1 : 8080 / metrics / has data.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-manager] lzhpo commented on issue #283: Pulsar Manager keeps saying "This environment is error. Please check it"

[GitBox]

lzhpo commented on issue #283:
URL: https://github.com/apache/pulsar-manager/issues/283#issuecomment-646424494


   I also encountered this problem. How did you solve it?
   My port is 8080, my curl-v http://127.0.0.1:8080/metrics/ has data.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-manager] lzhpo removed a comment on issue #283: Pulsar Manager keeps saying "This environment is error. Please check it"

[GitBox]

lzhpo removed a comment on issue #283:
URL: https://github.com/apache/pulsar-manager/issues/283#issuecomment-646424406


   I also encountered this problem. How did you solve it?
   My port is 8080, my curl-v http://127.0.0.1 : 8080 / metrics / has data.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSS] PIP-67: Contribute Pulsarctl to Apache Pulsar

[Dave Fisher]

Very cool!

This contribution may need to go through IP clearance. 
https://incubator.apache.org/ip-clearance/

Regards?
Dave

Sent from my iPhone

> On Jun 18, 2020, at 8:16 PM, Yong Zhang  wrote:
> 
> It seems that there are no objections to accepting this repo.
> 
> What should I do in the next step? Should I open a vote in a separate email?
> 
> Thanks
> 
> ---
>> On Mon, 15 Jun 2020 at 14:30, Guangning E  wrote:
>> 
>> Great job, +1, Thanks Yong and Xiaolong.
>> 
>> anonymitaet _  于2020年6月15日周一 上午9:56写道：
>> 
>>> Thanks Yong for this great job, +1
>>> 
>>> On 2020/6/15, 09:34, "PengHui Li"  wrote:
>>> 
>>>+1
>>>On Jun 15, 2020, 9:24 AM +0800, xiaolong ran <
>> ranxiaolong...@gmail.com>,
>>> wrote:
 Thanks Yong Zhang work for this, LGTM+1
 
 --
 Thanks
 Xiaolong Ran
 
> 在 2020年6月12日，上午11:38，Yong Zhang  写道：
> 
> Hi all,
> 
> We have developed a new tool Pulsarctl for managing Pulsar
>>> resources. It’s
> written in Golang
> and is an alternative tool of pulsar-admin. We’d like to
>>> contribute the
> project back to the Pulsar
> community.
> 
> ## Motivation
> 
> Pulsarctl is an alternative tool of pulsar-admin, used to manage
>>> resources
> in Apache Pulsar.
> Pulsarctl is written in Go and based on Pulsar REST API. It
>>> provides Go
> developers with API
> interface and user-friendly commands, making it easier to
>> interact
>>> with
> Pulsar brokers.
> 
> Compared with pulsar-admin, Pulsarctl is more user-friendly.
>>> Pulsarctl
> requires fewer dependencies
> to use commands and provides more comprehensive description and
>>> usage for
> commands.
> With Pulsarctl, users can find and resolve issues faster when
>>> errors occur.
> 
> ## Features
> 
> Pulsarctl not only integrates the Pulsar commands and BookKeeper
>>> commands
> but also
> provides some useful tools like output format and context
>>> management.
> 
> 
> ### Pulsar operations
> 
> For Pulsar operations, Pulsarctl integrates almost all the
>>> commands of
> pulsar-admin, including
> but not limited to the following operations:
> 
> - broker operations
> - cluster operations
> - tenant operations
> - namespace operations
> - topic operations
> - function operations
> - sink operations
> - source operations
> 
> Also, Pulsarctl supports the JWT(JSON Web Token) authentication
>>> and TLS
> authentication.
> 
> The following are command flags of Pulsarctl. You can use
>>> `--auth-params`
> to specify the auth
> params configured in pulsar-client. Or you can just specify
>>> `--token` to
> use that token to connect the broker.
> 
> ```
> Common flags:
> -s, --admin-service-url string The admin web service url that
> pulsarctl connects to. (default "http://localhost:8080";)
> --auth-params string Authentication parameters are used to
> configure the public and private key files required by tls
> For example:
> "tlsCertFile:val1,tlsKeyFile:val2"
> -C, --color string toggle colorized logs
> (true,false,fabulous) (default "true")
> -h, --help help for this command
> --tls-allow-insecure Allow TLS insecure connection
> --tls-trust-cert-path string Allow TLS trust cert file path
> --token string Using the token to authentication
> --token-file string Using the token file to authentication
> -v, --verbose int set log level, use 0 to silence, 4 for
> debugging (default 3)
> ```
> 
> ### BookKeeper operations
> 
> For BookKeeper operations, Pulsarctl integrates the commands
>>> listed in the
> [REST API](https://bookkeeper.apache.org/docs/4.10.0/admin/http/
>> )
> 
> - auto-recovery operations
> - bookie operations
> - bookies operations
> - ledger operations
> 
> 
> ### Save your configuration in the different contexts
> 
> Pulsarctl provides a context command which lets you manage your
>>> Pulsar
> cluster easier.
> The ‘context’ can save the different configurations of your
>> Pulsar
>>> cluster.
> And you can easily
> change to another cluster by the command `pulsarctl context use`.
>>> For more
> details please
> refer to
> 
>>> 
>> https://github.com/streamnative/pulsarctl/blob/master/docs/en/how-to-use-context.md
> 
> 
> ### Get different formats of the output
> 
> Pulsarctl provides an output flag `--output` to make the output
>>> transform
> into different
> formats, such as text, JSON, and YAML. The default view is the
>>> text which
> allows you
> to check the resources in your cluster directly. Also, you can
>> get
>>> the JSON
> or YAML
> format to do what you want to.
> 
> 
> ### Extend Pulsarctl using plugins easily
> 
> You can easily extend the Pulsarctl with a p

[GitHub] [pulsar-manager] lzhpo removed a comment on issue #283: Pulsar Manager keeps saying "This environment is error. Please check it"

[GitBox]

lzhpo removed a comment on issue #283:
URL: https://github.com/apache/pulsar-manager/issues/283#issuecomment-646424494


   I also encountered this problem. How did you solve it?
   My port is 8080, my curl-v http://127.0.0.1:8080/metrics/ has data.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-manager] lzhpo commented on issue #283: Pulsar Manager keeps saying "This environment is error. Please check it"

[GitBox]

lzhpo commented on issue #283:
URL: https://github.com/apache/pulsar-manager/issues/283#issuecomment-646425784


   @sijie @mikayeln 
   I have solved this problem. Do not use localhost or 127.0.0.1. Please use IP 
address, http://:8080, it will work! such as 
http://192.168.100.200:8080
   Hope it works for you!
   Thank you!



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Pulsar Client Go Release 0.1.1 Candidate 1

[Matteo Merli]

+1 (binding)
--
Matteo Merli


On Thu, Jun 18, 2020 at 6:00 AM lan.liang  wrote:
>
> +1 nb
>
>
>
>
>
>
>
>
> - lan.liang
> On 6/18/2020 17:20，ran leon wrote：
> +1 (non-binding)
>
> Thanks
> Leon
>
> On 2020/06/12 09:41:06, xiaolong ran  wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version 0.1.1, as 
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> This is the first release candidate for Apache Pulsar Go client, version 
> 0.1.1.
>
> It fixes the following issues:
> https://github.com/apache/pulsar-client-go/milestone/2?closed=1 
> 
>
> Pulsar Client Go's KEYS file contains PGP keys we used to sign this release:
>
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS 
> 
>
> Please download these packages and review this release candidate:
>
> - Download the source package (verify shasum, and asc) and follow the
> README.md to build and run the pulsar-client-go.
>
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval, with at least 3 PMC affirmative votes.
>
> Source file:
>
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.1.1-candidate-1/apache-pulsar-client-go-0.1.1-src.tar.gz
>  
> 
>
> The tag to be voted upon:
> v0.1.1-candidate-1
> https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1-candidate-1 
> 
>
> SHA-512 checksums:
> 2fed052f49364ccadbf912b360b4ce62ae63540d99b2d497eb8947808eceb8cea058e66f3968919c5f1b53937c3f5155a81b87b6160ea6a84309899481aaffa4
>   apache-pulsar-client-go-0.1.1-src.tar.gz

Re: [VOTE] Pulsar Client Go Release 0.1.1 Candidate 1

[Jia Zhai]

+1

Best Regards.


Jia Zhai

Beijing, China

Mobile: +86 15810491983




On Fri, Jun 19, 2020 at 1:34 PM Matteo Merli  wrote:

> +1 (binding)
> --
> Matteo Merli
> 
>
> On Thu, Jun 18, 2020 at 6:00 AM lan.liang  wrote:
> >
> > +1 nb
> >
> >
> >
> >
> >
> >
> >
> >
> > - lan.liang
> > On 6/18/2020 17:20，ran leon wrote：
> > +1 (non-binding)
> >
> > Thanks
> > Leon
> >
> > On 2020/06/12 09:41:06, xiaolong ran  wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version
> 0.1.1, as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > This is the first release candidate for Apache Pulsar Go client, version
> 0.1.1.
> >
> > It fixes the following issues:
> > https://github.com/apache/pulsar-client-go/milestone/2?closed=1 <
> https://github.com/apache/pulsar-client-go/milestone/2?closed=1>
> >
> > Pulsar Client Go's KEYS file contains PGP keys we used to sign this
> release:
> >
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
> >
> > Please download these packages and review this release candidate:
> >
> > - Download the source package (verify shasum, and asc) and follow the
> > README.md to build and run the pulsar-client-go.
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> >
> > Source file:
> >
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.1.1-candidate-1/apache-pulsar-client-go-0.1.1-src.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.1.0-candidate-1/apache-pulsar-client-go-0.1.0-src.tar.gz
> >
> >
> > The tag to be voted upon:
> > v0.1.1-candidate-1
> >
> https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1-candidate-1
> <
> https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1-candidate-1
> >
> >
> > SHA-512 checksums:
> >
> 2fed052f49364ccadbf912b360b4ce62ae63540d99b2d497eb8947808eceb8cea058e66f3968919c5f1b53937c3f5155a81b87b6160ea6a84309899481aaffa4
> apache-pulsar-client-go-0.1.1-src.tar.gz
>

Re: [VOTE] Pulsar Client Go Release 0.1.1 Candidate 1

[xiaolong ran]

The vote is now closed for Pulsar Client Go Release 0.1.1 Release Candidate 1
with 9 "+1" (3 +1 binding votes) votes, 0 +0/-0 votes, 0 -1 votes.

3 +1 bindings are:

- PengHui Li
- Matteo Merli
- Jia Zhai

6 +1 non-binding are:

- Guangning E
- Xiaolong Ran
- Cong Bo
- Yong Zhang
- Ian.liang
- ran leon
- Ming Luo

> 在 2020年6月19日，下午1:51，Jia Zhai  写道：
> 
> +1
> 
> Best Regards.
> 
> 
> Jia Zhai
> 
> Beijing, China
> 
> Mobile: +86 15810491983
> 
> 
> 
> 
> On Fri, Jun 19, 2020 at 1:34 PM Matteo Merli  wrote:
> 
>> +1 (binding)
>> --
>> Matteo Merli
>> 
>> 
>> On Thu, Jun 18, 2020 at 6:00 AM lan.liang  wrote:
>>> 
>>> +1 nb
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> - lan.liang
>>> On 6/18/2020 17:20，ran leon wrote：
>>> +1 (non-binding)
>>> 
>>> Thanks
>>> Leon
>>> 
>>> On 2020/06/12 09:41:06, xiaolong ran  wrote:
>>> Hi everyone,
>>> 
>>> Please review and vote on the release candidate #1 for the version
>> 0.1.1, as follows:
>>> [ ] +1, Approve the release
>>> [ ] -1, Do not approve the release (please provide specific comments)
>>> 
>>> This is the first release candidate for Apache Pulsar Go client, version
>> 0.1.1.
>>> 
>>> It fixes the following issues:
>>> https://github.com/apache/pulsar-client-go/milestone/2?closed=1 <
>> https://github.com/apache/pulsar-client-go/milestone/2?closed=1>
>>> 
>>> Pulsar Client Go's KEYS file contains PGP keys we used to sign this
>> release:
>>> 
>>> https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
>> https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
>>> 
>>> Please download these packages and review this release candidate:
>>> 
>>> - Download the source package (verify shasum, and asc) and follow the
>>> README.md to build and run the pulsar-client-go.
>>> 
>>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>> 
>>> Source file:
>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.1.1-candidate-1/apache-pulsar-client-go-0.1.1-src.tar.gz
>> <
>> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.1.0-candidate-1/apache-pulsar-client-go-0.1.0-src.tar.gz
>>> 
>>> 
>>> The tag to be voted upon:
>>> v0.1.1-candidate-1
>>> 
>> https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1-candidate-1
>> <
>> https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1-candidate-1
>>> 
>>> 
>>> SHA-512 checksums:
>>> 
>> 2fed052f49364ccadbf912b360b4ce62ae63540d99b2d497eb8947808eceb8cea058e66f3968919c5f1b53937c3f5155a81b87b6160ea6a84309899481aaffa4
>> apache-pulsar-client-go-0.1.1-src.tar.gz
>> 

[ANNOUNCE] Apache Pulsar Client Go 0.1.1 released

[xiaolong ran]

The Apache Pulsar team is proud to announce Apache Pulsar Client Go version 
0.1.1.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

For Pulsar Client Go release details, visit:

https://github.com/apache/pulsar-client-go/releases/tag/v0.1.1 


We would like to thank the contributors that made the release possible.

Regards,

The Pulsar Team

[GitHub] [pulsar-client-node] k2la commented on issue #94: Message ID for produced messages

[GitBox]

k2la commented on issue #94:
URL: 
https://github.com/apache/pulsar-client-node/issues/94#issuecomment-646471593


   There is not such a way at present but we will support it in the future.
   It may take some time to support it as `pulsar-client-cpp` needs to be 
modified.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org