[VOTE] DotPulsar Release 3.3.2-rc.1

2024-07-17 Thread David Jensen
Hi everyone,

Please review and vote on the release candidate for the version 3.3.2, as 
follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

DotPulsar's KEYS file contains the PGP keys we used to sign this release:
https://downloads.apache.org/pulsar/KEYS

Please download these packages and review this release candidate:
- Review release notes
- Download the source package (verify shasum, and asc) and follow the
README.md to build and run DotPulsar.

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

Guide for Validating DotPulsar Release on Linux and MacOS
https://github.com/apache/pulsar-dotpulsar/blob/master/docs/release_validation_linux_macos.md

Source file:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-dotpulsar-3.3.2-rc.1/

Nuget package:
https://www.nuget.org/packages/DotPulsar/3.3.2-rc.1

The tag to be voted upon:
https://github.com/apache/pulsar-dotpulsar/tree/3.3.2-rc.1

SHA-512 checksums:
bfafafb71e16b727661d07127b2d3bf84fe41c149fb408e53da70b6b3523accdb984b26c205edcc7fc7aab000d7013f86730e4aaabb40c69a26d70a89d30c476
  pulsar-dotpulsar-3.3.2-src.tar.gz


Re: Clarification on deadLetterPolicy Attribute in the ConsumerConfigurationData class

2024-07-17 Thread Anurag Reddy Karri
Dear Apache Pulsar Team,

I hope this email finds you well. I am writing to seek clarification
regarding the *deadLetterPolicy* attribute in the
*ConsumerConfigurationData* class within Apache Pulsar.

As a user of Apache Pulsar, we have been utilizing *PulsarSpout* exposed by
the pulsar-storm adaptor within an Apache Storm topology for message
consumption from Pulsar topics. Recently, we encountered an issue where the
*deadLetterPolicy* that we set on the *PulsarSpout* seems to be lost when
the topology is started. Upon investigation, we found that the
*deadLetterPolicy* attribute in *ConsumerConfigurationData* is marked as
*transient*.

Due to Storm topologies being serialized and transferred from the nimbus to
workers for execution, the transient nature of this attribute results in
the loss of our specified configuration. Could you kindly provide insights
into why this attribute is marked as transient and how we can ensure that
the *deadLetterPolicy* configuration persists across the serialization
process in Apache Storm?

We believe that implementing the *java.io.Serializable* interface in the
*DeadLetterPolicy* class should eliminate the need for the *transient*
keyword. If this is accurate, we are prepared to submit a pull request
accordingly.

Any advice or best practices for managing this scenario within Apache Storm
using Pulsar would be greatly appreciated.

Thank you very much for your assistance. Looking forward to your response.

Best regards,
Anurag

-- 


*-*

*This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error, please notify the 
system manager. This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee, 
you should not disseminate, distribute or copy this email. Please notify 
the sender immediately by email if you have received this email by mistake 
and delete this email from your system. If you are not the intended 
recipient, you are notified that disclosing, copying, distributing or 
taking any action in reliance on the contents of this information is 
strictly prohibited.*

 

*Any views or opinions presented in this 
email are solely those of the author and do not necessarily represent those 
of the organization. Any information on shares, debentures or similar 
instruments, recommended product pricing, valuations and the like are for 
information purposes only. It is not meant to be an instruction or 
recommendation, as the case may be, to buy or to sell securities, products, 
services nor an offer to buy or sell securities, products or services 
unless specifically stated to be so on behalf of the Flipkart group. 
Employees of the Flipkart group of companies are expressly required not to 
make defamatory statements and not to infringe or authorise any 
infringement of copyright or any other legal right by email communications. 
Any such communication is contrary to organizational policy and outside the 
scope of the employment of the individual concerned. The organization will 
not accept any liability in respect of such communication, and the employee 
responsible will be personally liable for any damages or other liability 
arising.*

 

*Our organization accepts no liability for the 
content of this email, or for the consequences of any actions taken on the 
basis of the information *provided,* unless that information is 
subsequently confirmed in writing. If you are not the intended recipient, 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.*

_-_


Re: [DISCUSS] Cherry-pick PIP-364: Introduce a new load balance algorithm AvgShedder.

2024-07-17 Thread WenZhi Feng
Hi all,
  The thread will keep open for 48 hours.
  If there is no objections,I will perform the cherry-picking.

Thanks,
Wenzhi Feng.

On 2024/07/16 09:43:30 WenZhi Feng wrote:
> link: https://github.com/apache/pulsar/pull/22949
> 
> On 2024/07/16 09:41:17 thetumbled wrote:
> > Hi all,
> > I would like to start a discussion to cherry-pick PIP-364: Introduce a new 
> > load balance algorithm AvgShedder into branch-3.0, branch-3.2, and 
> > branch-3.3.
> > This PIP introduce a new load balance algorithm with higher bundle 
> > switching accuracy and stablity.
> > 
> > Thanks,
> > Wenzhi Feng.
>