Re?? [Vote] PIP 126: Support custom and pluggable consumer selector

[zhangao]

Here is the proposal:
https://github.com/apache/pulsar/issues/13473


--  --
??: 
   "dev"

Re: [ANNOUNCE] Apache Pulsar 2.9.1 released

[Dianjin Wang]

Great! Thanks to all the contributors that made this release happen.

Best,
Dianjin Wang


On Fri, Dec 24, 2021 at 3:18 PM Enrico Olivelli 
wrote:

> The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.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 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
>

[DISCUSS] PIP-124: Pulsar Client Shared State API

[Enrico Olivelli]

Hello everyone,
I want to start a discussion about PIP-124 Pulsar Client Shared  State API

This is the PIP document
https://github.com/apache/pulsar/issues/13490

This is a demo implementation (a proof-of-concept):
https://github.com/eolivelli/pulsar-shared-state-manager

Please take a look and share your thoughts

I believe that this will unlock the potential of the Exclusive
Producer and it will also make easier the life of many developers who
are using Pulsar and need some API to share configuration, metadata,
or any simple key-value data structure without adding a Database or
other components to their library, Pulsar IO connector or Pulsar
Protocol Handler.

Thanks
Enrico

Re: [ANNOUNCE] Apache Pulsar 2.9.1 released

[陳智弘]

I am really appreciate those contributors and volunteers to make this
release happen!

Dianjin Wang  於 2021年12月24日 週五 16:43 寫道：

> Great! Thanks to all the contributors that made this release happen.
>
> Best,
> Dianjin Wang
>
>
> On Fri, Dec 24, 2021 at 3:18 PM Enrico Olivelli 
> wrote:
>
> > The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.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 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-client-node] Sraleik commented on issue #99: Authenticating using a Token

[GitBox]

Sraleik commented on issue #99:
URL: 
https://github.com/apache/pulsar-client-node/issues/99#issuecomment-1000809752


   It is now working for me with this setup: 
   
   node version:  16.13.0
   pulsar-client-node: 1.5.0
   apache-pulsar-client(library C++): 2.9.1
   
   with apache-pulsar-client: 2.8.0 it was not working


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

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

Re: [broker]loadBalancerMemoryResourceWeight config default value optimiz

[Haiting Jiang]

Agreed on the default settings would cause some unnecessary bundle shedding.
But I believe that disable it by default is not the best option here.

I would like share some preliminary thoughts on this,

1) About memory usage definition, we can try to use the memory usage just after 
last GC 
instead of instant memory usage,  like com.sun.management.GcInfo#usageAfterGc 
[1], 
although it depends on JVM platform.

2) About the default value. Normally, we have an expected max heap memory usage 
for a
Java Application. For example, In pulsar we enables UseG1GC by default, and 
with G1GC
we have InitiatingHeapOccupancyPercent = 45 by default. It will start a GC when 
heap 
usage is greater than 45%. If heap usage is over 45%, then it means it's under 
heavy load 
and we should do some load shedding. So We can set the 
loadBalancerMemoryResourceWeight
to 0.45 or leave some margin like 0.5.

[1] 
https://docs.oracle.com/en/java/javase/12/docs/api/jdk.management/com/sun/management/GcInfo.html
[2] 
https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/g1_gc.html

Thanks,
Haiting Jiang


On 2021/12/24 01:57:37 jiangxinwei wrote:
> https://github.com/apache/pulsar/pull/13464
> 
>  
> 
> Pasted below for quoting convenience. ---
> 
>  
> 
> Motivation
> 
> memory.percentUsage() value is depends on the gc trigger moment, this value
> has a random affect on ThresholdShedder loadBalancer strategy. it is a
> meaningless dimension
> 
> the usage data from one broker
> 
>  
>  89d-9f98-b44205a43f8c.png> 
> 
> solution
> 
> set loadBalancerMemoryResourceWeight=0.0
> 
> 
> 
> -- 
> Avast 防毒软件已对此电子邮件执行病毒检查。
> https://www.avast.com/antivirus
> 

[GitHub] [pulsar-client-node] Matt-Esch commented on issue #99: Authenticating using a Token

[GitBox]

Matt-Esch commented on issue #99:
URL: 
https://github.com/apache/pulsar-client-node/issues/99#issuecomment-1000845729


   Trying with v2.9.1 as per @Sraleik suggestion
   
   ```
   [2021-12-24T13:39:43.164Z] 2021-12-24 13:39:42.898 INFO  [139633915127552] 
ClientImpl:491 | Closing Pulsar client with 0 producers and 0 consumers
   [2021-12-24T13:39:43.164Z] 2021-12-24 13:39:42.898 INFO  [139633681757952] 
ClientConnection:181 | [ -> pulsar+ssl://localhost:6651] Create 
ClientConnection, timeout=1
   [2021-12-24T13:39:43.164Z] 2021-12-24 13:39:42.898 INFO  [139633681757952] 
ConnectionPool:96 | Created connection for pulsar+ssl://localhost:6651
   [2021-12-24T13:39:43.164Z] 2021-12-24 13:39:42.898 INFO  [139633915127552] 
ClientConnection:1535 | [ -> pulsar+ssl://localhost:6651] Connection 
closed
   [2021-12-24T13:39:43.164Z] Segmentation fault (core dumped)
   [2021-12-24T13:39:43.164Z] Exited with code: 139.
   [2021-12-24T13:39:43.164Z] Error executing child process: Error: Process 
exited with code 139.
   ```


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

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

Re: [ANNOUNCE] Apache Pulsar 2.9.1 released

[mattison chao]

great work!

On Fri, 24 Dec 2021 at 19:23, 陳智弘  wrote:

> I am really appreciate those contributors and volunteers to make this
> release happen!
>
> Dianjin Wang  於 2021年12月24日 週五 16:43 寫道：
>
> > Great! Thanks to all the contributors that made this release happen.
> >
> > Best,
> > Dianjin Wang
> >
> >
> > On Fri, Dec 24, 2021 at 3:18 PM Enrico Olivelli 
> > wrote:
> >
> > > The Apache Pulsar team is proud to announce Apache Pulsar version
> 2.9.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 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
> > >
> >
>