equanz commented on pull request #6996:
URL: https://github.com/apache/pulsar/pull/6996#issuecomment-635122287
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
aloyszhang opened a new pull request #7079:
URL: https://github.com/apache/pulsar/pull/7079
### Motivation
fix typos in java doc
This is an automated message from the Apache Git Service.
To respond to the message,
aloyszhang opened a new pull request #7078:
URL: https://github.com/apache/pulsar/pull/7078
Fixes #6975
Master Issue: #6975
### Motivation
Enable precise topic publish rate limit on broker.
Now pulsar limits publish rate of topic by a period task runs
codelipenghui commented on pull request #6052:
URL: https://github.com/apache/pulsar/pull/6052#issuecomment-635104385
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
codelipenghui commented on pull request #6791:
URL: https://github.com/apache/pulsar/pull/6791#issuecomment-635104421
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
merlimat opened a new pull request #7077:
URL: https://github.com/apache/pulsar/pull/7077
### Motivation
When we're increasing the number of partitions in a topic, we typically also
pre-create the subscriptions on those topics. In this case, we're also
pre-creating the non-durable
This is an automated email from the ASF dual-hosted git repository.
mmerli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 55f7fd6 Fixed updating partitioned topic
merlimat merged pull request #7064:
URL: https://github.com/apache/pulsar/pull/7064
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
ckdarby commented on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635081278
@ashwallace Thanks for everything. I'll nuke the cluster & change the type
with a baseline higher and let you know.
Here are my other comments...
>In your graphs, bookie
equanz commented on pull request #6996:
URL: https://github.com/apache/pulsar/pull/6996#issuecomment-635076014
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
codelipenghui commented on pull request #6052:
URL: https://github.com/apache/pulsar/pull/6052#issuecomment-635075286
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
DGBStarSky opened a new issue #7076:
URL: https://github.com/apache/pulsar/issues/7076
**Describe the bug**
Pulsar SQL cannot get the latest message of topic.
**To Reproduce**
Steps to reproduce the behavior:
I use pulsar sql query messages, but cannot get the latest
DGBStarSky closed issue #7076:
URL: https://github.com/apache/pulsar/issues/7076
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
ashwallace commented on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635066612
>
>
> @ashwallace But that doesn't explain why when on the pod itself using `dd`
I'm able to access the EBS at 200 mbyte/s.
>
> I will change the cluster to one that
gh77 commented on issue #4937:
URL: https://github.com/apache/pulsar/issues/4937#issuecomment-635062518
> @gh77 what version of python function are you using?
Sorry to reply so late. I use python 3.8.2. Now the issue has gone.
I suspect the problem has to do with
merlimat opened a new pull request #7075:
URL: https://github.com/apache/pulsar/pull/7075
### Motivation
The test has been failing frequently in CI with this error:
```
[ERROR]
testUpdateGlobalTopicPartition(org.apache.pulsar.broker.service.ReplicatorTest)
Time elapsed:
codelipenghui commented on pull request #6052:
URL: https://github.com/apache/pulsar/pull/6052#issuecomment-635059385
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
This is an automated email from the ASF dual-hosted git repository.
sanjeevrk pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git.
from adf650e fixes RESTAPIs and Cli button not working. (#7038)
add afd3296 Fix the flaky function test.
srkukarni merged pull request #7057:
URL: https://github.com/apache/pulsar/pull/7057
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
ckdarby edited a comment on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635048127
@ashwallace But that doesn't explain why when on the pod itself using `dd`
I'm able to access the EBS at 200 mbyte/s.
I will change the cluster to one that has
ckdarby commented on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635048127
@ashwallace But that doesn't explain why when on the pod itself using `dd`
I'm able to access the EBS at 200 mbyte/s.
I will change the cluster to one that has throughput has
merlimat opened a new pull request #7074:
URL: https://github.com/apache/pulsar/pull/7074
### Motivation
Currently if authorization is not enforced, the AuthZ plugin is not loaded
at all. That makes it impossible to switch a cluster from no-authz to
authz-enforced with no downtime.
sijie commented on issue #7056:
URL: https://github.com/apache/pulsar/issues/7056#issuecomment-635043934
@sakthi-prasad I think the documentation of release 2.5.2 was cut by using
the latest master. @jiazhai is looking into fixing the issue.
wolfstudy merged pull request #263:
URL: https://github.com/apache/pulsar-client-go/pull/263
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
wolfstudy closed issue #240:
URL: https://github.com/apache/pulsar-client-go/issues/240
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
This is an automated email from the ASF dual-hosted git repository.
rxl pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-client-go.git
The following commit(s) were added to refs/heads/master by this push:
new bf248fd [Issue 240] Add check for max
sijie commented on issue #7055:
URL: https://github.com/apache/pulsar/issues/7055#issuecomment-635041688
@Saswatibhoi
How do you deploy your pulsar cluster? Did you happen to run any bookkeeper
commands like `metaformat` to format the bookkeeper metadata?
wolfstudy commented on issue #264:
URL:
https://github.com/apache/pulsar-client-go/issues/264#issuecomment-635039803
@keithnull will track this task
This is an automated message from the Apache Git Service.
To respond to
merlimat opened a new pull request #7073:
URL: https://github.com/apache/pulsar/pull/7073
### Motivation
There was a race in testRelativeMessageRateLimitingThrottling where
the test was sending and receiving a message to warmup the broker, and
then testing whether messages
equanz commented on pull request #6996:
URL: https://github.com/apache/pulsar/pull/6996#issuecomment-635038553
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
wolfstudy commented on a change in pull request #263:
URL: https://github.com/apache/pulsar-client-go/pull/263#discussion_r431529838
##
File path: pulsar/producer_partition.go
##
@@ -236,6 +239,16 @@ func (p *partitionProducer) internalSend(request
*sendRequest) {
merlimat opened a new pull request #7072:
URL: https://github.com/apache/pulsar/pull/7072
### Motivation
All tests in Replicator test use the same instance of pulsar and same
namespaces. Depending on the order the tests run in, which is somewhat
random, the backlog quota may be
wolfstudy commented on a change in pull request #263:
URL: https://github.com/apache/pulsar-client-go/pull/263#discussion_r431529838
##
File path: pulsar/producer_partition.go
##
@@ -236,6 +239,16 @@ func (p *partitionProducer) internalSend(request
*sendRequest) {
wolfstudy commented on a change in pull request #263:
URL: https://github.com/apache/pulsar-client-go/pull/263#discussion_r431529838
##
File path: pulsar/producer_partition.go
##
@@ -236,6 +239,16 @@ func (p *partitionProducer) internalSend(request
*sendRequest) {
wolfstudy opened a new issue #264:
URL: https://github.com/apache/pulsar-client-go/issues/264
Currently, there are some inconsistencies in the handling of errors. In
order to ensure the structured output of the log, we should use withError()
instead of Error().
E.g:
```
merlimat opened a new pull request #7071:
URL: https://github.com/apache/pulsar/pull/7071
### Motivation
A bunch of tests were using 100ms as the timeout for receive. 100ms is
way too short. The broker for these tests is standalone, so everything
is running in one process on
wolfstudy commented on a change in pull request #263:
URL: https://github.com/apache/pulsar-client-go/pull/263#discussion_r431529838
##
File path: pulsar/producer_partition.go
##
@@ -236,6 +239,16 @@ func (p *partitionProducer) internalSend(request
*sendRequest) {
merlimat opened a new pull request #7070:
URL: https://github.com/apache/pulsar/pull/7070
### Motivation
This adds the support for refreshing the auth credentials in C++ clients for
PIP-55:
https://github.com/apache/pulsar/wiki/PIP-55%3A-Refresh-Authentication-Credentials
.
merlimat opened a new pull request #7069:
URL: https://github.com/apache/pulsar/pull/7069
### Motivation
The topics used in a bunch of the cases in `BasicEndToEndTest` had no
unique identifier, so if you ran it multiple times against the same
standalone cluster, they would
merlimat opened a new pull request #7068:
URL: https://github.com/apache/pulsar/pull/7068
### Motivation
`ClientImpl::handleClose` was using static variables to record the first
error on closing a client. This is just wrong. A static stack variable
in c++ acts like a global. So
merlimat opened a new pull request #7067:
URL: https://github.com/apache/pulsar/pull/7067
### Motivation
This works around the issue where if the hostname of the machine has an
underscore,
the test will fail to run
ashwallace edited a comment on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635024332
@ckdarby @sijie
EC2 r5.large has a baseline EBS throughput of ~81 MB/s at 128 KB IO sizes.
Looks like you're at around that number more or less.
Because of this fact,
ashwallace edited a comment on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635024332
@ckdarby @sijie
EC2 r5.large has a baseline EBS throughput of ~81 MB/s at 128 KB IO sizes.
Looks like you're at around that number more or less.
Because of this fact,
merlimat opened a new pull request #7066:
URL: https://github.com/apache/pulsar/pull/7066
### Motivation
When you trigger Runtime#halt from a test, as was happening on ZK
session loss, it kills the test without reporting a result. We
shouldn't do that. Instead, reserve halt for
ashwallace commented on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635024332
EC2 r5.large has a baseline EBS throughput of ~81 MB/s at 128 KB IO sizes.
Looks like you're at around that number more or less.
Because of this fact, you may not be a benefit
merlimat opened a new pull request #7065:
URL: https://github.com/apache/pulsar/pull/7065
### Motivation
When a namespace bundle split operation fails by timeout, we're not cleaning
up the current in-memory metadata of the old bundles. This lead to the broker
to treat the operation
keithnull commented on issue #231:
URL:
https://github.com/apache/pulsar-client-go/issues/231#issuecomment-635021070
Seems this has already been fixed by #229?
This is an automated message from the Apache Git Service.
To
zhanghaou commented on issue #7049:
URL: https://github.com/apache/pulsar/issues/7049#issuecomment-635020327
Thanks for your feedback, I will fix it.
This is an automated message from the Apache Git Service.
To respond to
merlimat opened a new pull request #7064:
URL: https://github.com/apache/pulsar/pull/7064
### Motivation
The underlying issue was already fixed in master, though currently there is
no test to validate that we can increase partitions on a topic without
subscriptions.
merlimat opened a new pull request #7063:
URL: https://github.com/apache/pulsar/pull/7063
### Motivation
Some tests had @Test at the class level and also at the method
level. This resulted in these tests running twice.
merlimat opened a new pull request #7062:
URL: https://github.com/apache/pulsar/pull/7062
### Motivation
C++ consumers are using a queue size of 1000 when consuming from multiple
topics (eg: regex), irrespectively of the setting configured in the
`ConsumerConfiguration` that is
merlimat opened a new pull request #7061:
URL: https://github.com/apache/pulsar/pull/7061
### Motivation
The run-unit-tests.sh assumed that the build tree was at /pulsar as it
is in the docker based build. This isn't necessarily the case when the
script is being called
merlimat opened a new pull request #7060:
URL: https://github.com/apache/pulsar/pull/7060
### Motivation
In order to have a predictable memory footprint in brokers, we need to cap
the amount of bytes that we read in single range read request from BK.
Since BK doesn't take a
ckdarby commented on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635011079
Talked to @cdbartholomew today and he mentioned that he might be having what
appears to be the same issue, but in Azure.
Read performance is nowhere close to the disk
merlimat commented on pull request #6791:
URL: https://github.com/apache/pulsar/pull/6791#issuecomment-635000206
@sijie @codelipenghui Added configuration switch for consistent hashing, by
default turned off. PTAL.
This is
irairdon opened a new issue #7059:
URL: https://github.com/apache/pulsar/issues/7059
When running pulsar on Kubernetes if you reboot a Kubernetes node any client
producing will hand and be unable to produce new messages.
**To Reproduce**
Steps to reproduce the behavior:
1.
sijie closed issue #7002:
URL: https://github.com/apache/pulsar/issues/7002
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
This is an automated email from the ASF dual-hosted git repository.
sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new adf650e fixes RESTAPIs and Cli button not
sijie merged pull request #7038:
URL: https://github.com/apache/pulsar/pull/7038
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
ckdarby commented on issue #7058:
URL: https://github.com/apache/pulsar/issues/7058#issuecomment-634959473
@sijie I was finally able to compile the issue that I mentioned on Slack.
This is an automated message from the
ckdarby opened a new issue #7058:
URL: https://github.com/apache/pulsar/issues/7058
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. We're using Pulsar helm install on AWS EKS
rdhabalia commented on pull request #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-634940827
> We can do here:
>
> a) use a feature flag to control whether include reader cursors in the
storage quota consideration; b) if you don’t want to introduce the feature
jerrypeng merged pull request #7052:
URL: https://github.com/apache/pulsar/pull/7052
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
This is an automated email from the ASF dual-hosted git repository.
jerrypeng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new fb182c0 Remove function files stored in BK
rdhabalia commented on pull request #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-634895127
Pulsar reader is a non-durable cursor which means
1. Broker should not persist data because of non-durable cursor's existence
but broker should allow non-durable cursor to
sijie commented on pull request #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-634892636
> I have already heard from members of industry/community that there are too
many tunables in Pulsar and its hard for people to navigate.
Well, "tuneables" are
jerrypeng commented on pull request #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-634870390
@sijie @merlimat maybe we can ask others for opinions? @rdhabalia @joefk
can you share your opinion on this issue as well?
srkukarni commented on pull request #7057:
URL: https://github.com/apache/pulsar/pull/7057#issuecomment-634836819
@jerrypeng done
This is an automated message from the Apache Git Service.
To respond to the message, please
jerrypeng commented on pull request #7057:
URL: https://github.com/apache/pulsar/pull/7057#issuecomment-634831106
@srkukarni the test should also be deleted flaky tests
https://github.com/apache/pulsar/blob/master/.github/workflows/ci-unit-flaky.yaml#L84
and removed from:
merlimat merged pull request #7034:
URL: https://github.com/apache/pulsar/pull/7034
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
This is an automated email from the ASF dual-hosted git repository.
mmerli pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git.
from d68829c Add properties for managed-ledger. (#7054)
add a50b75a Fix Result can't be serialized to string
srkukarni opened a new pull request #7057:
URL: https://github.com/apache/pulsar/pull/7057
*(If this PR fixes a github issue, please add `Fixes #`.)*
Fixes #
*(or if this PR is one task of a github issue, please add `Master Issue:
#` to link to the master issue.)*
rueian commented on a change in pull request #248:
URL: https://github.com/apache/pulsar-client-go/pull/248#discussion_r431291341
##
File path: pulsar/internal/connection.go
##
@@ -656,18 +662,20 @@ func (c *connection) Close() {
c.log.Info("Connection closed")
Saswatibhoi closed issue #6644:
URL: https://github.com/apache/pulsar/issues/6644
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
sakthi-prasad opened a new issue #7056:
URL: https://github.com/apache/pulsar/issues/7056
When running pulsar client cli command for consumer, --subscription-position
is shown as unknown option
Note pulsar client version: 2.5.2
Run the below command to start a consumer
BewareMyPower commented on issue #6945:
URL: https://github.com/apache/pulsar/issues/6945#issuecomment-634739076
You could create multiple producers and deliver the message to the right
producer associated with the key.
**However, I suspected that it's broker's problem.** Here is my
Saswatibhoi opened a new issue #7055:
URL: https://github.com/apache/pulsar/issues/7055
**Describe the bug**
While producing messages on a topic, it is trying to reach to a ledger that
doesn't exists. The produce operation fails throwing an error message "No such
ledger exists on
codelipenghui commented on pull request #4955:
URL: https://github.com/apache/pulsar/pull/4955#issuecomment-634647772
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
This is an automated email from the ASF dual-hosted git repository.
penghui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new d68829c Add properties for managed-ledger.
codelipenghui merged pull request #7054:
URL: https://github.com/apache/pulsar/pull/7054
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
nicolo-paganin removed a comment on pull request #6895:
URL: https://github.com/apache/pulsar/pull/6895#issuecomment-634630347
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To
nicolo-paganin commented on pull request #6895:
URL: https://github.com/apache/pulsar/pull/6895#issuecomment-634630347
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
hangc0276 commented on pull request #6719:
URL: https://github.com/apache/pulsar/pull/6719#issuecomment-634624662
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
nicolo-paganin removed a comment on pull request #6895:
URL: https://github.com/apache/pulsar/pull/6895#issuecomment-634592624
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To
nicolo-paganin commented on pull request #6895:
URL: https://github.com/apache/pulsar/pull/6895#issuecomment-634592624
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
Anonymitaet commented on pull request #6942:
URL: https://github.com/apache/pulsar/pull/6942#issuecomment-634566358
Doc added https://github.com/apache/pulsar/pull/7051.
This is an automated message from the Apache Git
codelipenghui edited a comment on pull request #6977:
URL: https://github.com/apache/pulsar/pull/6977#issuecomment-634564244
@feeblefakie #6791 introduces a consistent hash approach for the consumer
selector. The current implementation is a hash range split approach.
This PR is to
Anonymitaet commented on pull request #7051:
URL: https://github.com/apache/pulsar/pull/7051#issuecomment-634565117
@codelipenghui thank you
This is an automated message from the Apache Git Service.
To respond to the
codelipenghui commented on pull request #6977:
URL: https://github.com/apache/pulsar/pull/6977#issuecomment-634564244
@feeblefakie #6791 introduces a consistent hash approach for the consumer
selector. The current implementation is a hash range split approach.
feeblefakie commented on pull request #6977:
URL: https://github.com/apache/pulsar/pull/6977#issuecomment-634546905
@codelipenghui
Just a question.
So this and #6791 are solving the same issue with different approaches but
the both will be applied ?
#6791 looks like more
Huanli-Meng commented on pull request #6977:
URL: https://github.com/apache/pulsar/pull/6977#issuecomment-634532636
should the key_shared subscription in messaging section be updated?
This is an automated message from the
codelipenghui opened a new pull request #7054:
URL: https://github.com/apache/pulsar/pull/7054
### Motivation
Add properties for managed-ledger.
### Verifying this change
New unit tests added
### Does this pull request potentially affect one of the following
Huanli-Meng commented on pull request #7053:
URL: https://github.com/apache/pulsar/pull/7053#issuecomment-634522017
Update the Pulsar 2.5.2 sidebar doc to
1. add Run Pulsar in Kubernetes doc to Get started section
2: remove the blank page for Connector Admin CLI from the Reference
Huanli-Meng opened a new pull request #7053:
URL: https://github.com/apache/pulsar/pull/7053
*(If this PR fixes a github issue, please add `Fixes #`.)*
Fixes #
*(or if this PR is one task of a github issue, please add `Master Issue:
#` to link to the master issue.)*
codelipenghui commented on pull request #4955:
URL: https://github.com/apache/pulsar/pull/4955#issuecomment-634495498
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
codelipenghui commented on pull request #6347:
URL: https://github.com/apache/pulsar/pull/6347#issuecomment-634495475
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
This is an automated email from the ASF dual-hosted git repository.
penghui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 8ffee4c Add advertisedAddress and
codelipenghui merged pull request #7051:
URL: https://github.com/apache/pulsar/pull/7051
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
huangdx0726 commented on pull request #5716:
URL: https://github.com/apache/pulsar/pull/5716#issuecomment-634494100
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
huangdx0726 commented on pull request #7042:
URL: https://github.com/apache/pulsar/pull/7042#issuecomment-634494191
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
1 - 100 of 107 matches
Mail list logo
