[GitHub] [pulsar-manager] youzipi commented on issue #473: fail to create environment as broker throw error: `io.netty.handler.codec.TooLongFrameException`

2022-07-18 Thread GitBox
youzipi commented on issue #473: URL: https://github.com/apache/pulsar-manager/issues/473#issuecomment-1188671403 use the wrong url found this in manager backend log: ```js Create Pulsar Admin instance. url=http://pulsar:6650, authPlugin=, authParams=, tlsAllowInsecureConnection

[GitHub] [pulsar-site] tisonkun commented on pull request #148: Remove locales we don't support yet

2022-07-18 Thread GitBox
tisonkun commented on PR #148: URL: https://github.com/apache/pulsar-site/pull/148#issuecomment-1188619227 @Anonymitaet thank you. Then I'm waiting for more review comments. The original purpose to make this change is "If we don't support it, we don't mention it". Even if we _have a p

[GitHub] [pulsar-site] Anonymitaet commented on pull request #148: Remove locales we don't support yet

2022-07-18 Thread GitBox
Anonymitaet commented on PR #148: URL: https://github.com/apache/pulsar-site/pull/148#issuecomment-1188605008 If you want to preview changes locally, then `./preview.sh` is OK and enough -- This is an automated message from the Apache Git Service. To respond to the message, please log on t

[GitHub] [pulsar-manager] youzipi opened a new issue, #473: fail to create environment as broker throw error: `io.netty.handler.codec.TooLongFrameException`

2022-07-18 Thread GitBox
youzipi opened a new issue, #473: URL: https://github.com/apache/pulsar-manager/issues/473 when i create new environment, got error: `This environment is error. Please check it` container log: ``` pulsar_1 | 2022-07-19T04:57:04,910+ [pulsar-io-31-4] WARN org.apache

[GitHub] [pulsar-site] tisonkun commented on pull request #148: Remove locales we don't support yet

2022-07-18 Thread GitBox
tisonkun commented on PR #148: URL: https://github.com/apache/pulsar-site/pull/148#issuecomment-1188570313 @Anonymitaet I make this patch with intention to avoid display language options which we don't have a real translated content. However, I don't know whether I change it correctly. I'd

[GitHub] [pulsar-site] Anonymitaet commented on pull request #148: Remove locales we don't support yet

2022-07-18 Thread GitBox
Anonymitaet commented on PR #148: URL: https://github.com/apache/pulsar-site/pull/148#issuecomment-1188567099 @tisonkun double check: do you want to preview localized pages? Seems that they can not be previewed, correct? @urfreespace -- This is an automated message from the Apache Git Se

[GitHub] [pulsar-site] tisonkun commented on pull request #148: Remove locales we don't support yet

2022-07-18 Thread GitBox
tisonkun commented on PR #148: URL: https://github.com/apache/pulsar-site/pull/148#issuecomment-1188492252 @Anonymitaet thanks for your reaction. Since we don't run any CI tasks to dry run and verify the build, may I ask how to verify all changes looks good locally? I've run `./preview.sh`,

[GitHub] [pulsar-site] tisonkun opened a new pull request, #148: Remove locales we don't support yet

2022-07-18 Thread GitBox
tisonkun opened a new pull request, #148: URL: https://github.com/apache/pulsar-site/pull/148 Otherwise when a user change the language but found the result is just English, it's not a good experience. If we don't support it, we don't mention it. We can also add them back when there

[GitHub] [pulsar-helm-chart] mattisonchao merged pull request #277: Bump Apache Pulsar version to 2.9.3

2022-07-18 Thread GitBox
mattisonchao merged PR #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277 -- 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...@p

[GitHub] [pulsar-helm-chart] mattisonchao commented on pull request #277: Bump Apache Pulsar version to 2.9.3

2022-07-18 Thread GitBox
mattisonchao commented on PR #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277#issuecomment-1187452537 > I guess tags referencing `2.9.2` should also be updated in `.ci/clusters/values-pulsar-image.yaml` file. It might be better to remove the tags from that file so that it's

[GitHub] [pulsar-helm-chart] lhotari commented on pull request #277: Bump Apache Pulsar version to 2.9.3

2022-07-18 Thread GitBox
lhotari commented on PR #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277#issuecomment-1187443859 I guess tags referencing `2.9.2` should also be updated in `.ci/clusters/values-pulsar-image.yaml` file. -- This is an automated message from the Apache Git Service. To respond

[GitHub] [pulsar-helm-chart] mattisonchao commented on pull request #277: Bump Apache Pulsar version to 2.9.3

2022-07-18 Thread GitBox
mattisonchao commented on PR #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277#issuecomment-1187442014 > pulsar_metadata.image.tag fixed, thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use th

[GitHub] [pulsar-helm-chart] mattisonchao commented on a diff in pull request #277: Bump Apache Pulsar version to 2.9.3

2022-07-18 Thread GitBox
mattisonchao commented on code in PR #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277#discussion_r923376333 ## charts/pulsar/Chart.yaml: ## @@ -18,7 +18,7 @@ # apiVersion: v2 -appVersion: "2.9.2" +appVersion: "2.9.3" description: Apache Pulsar Helm chart for

[GitHub] [pulsar-helm-chart] lhotari commented on a diff in pull request #277: Bump Apache Pulsar version to 2.9.3

2022-07-18 Thread GitBox
lhotari commented on code in PR #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277#discussion_r923370490 ## charts/pulsar/Chart.yaml: ## @@ -18,7 +18,7 @@ # apiVersion: v2 -appVersion: "2.9.2" +appVersion: "2.9.3" description: Apache Pulsar Helm chart for Kuber

[GitHub] [pulsar-helm-chart] lhotari commented on a diff in pull request #277: Bump Apache Pulsar version to 2.9.3

2022-07-18 Thread GitBox
lhotari commented on code in PR #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277#discussion_r923368906 ## charts/pulsar/Chart.yaml: ## @@ -18,7 +18,7 @@ # apiVersion: v2 -appVersion: "2.9.2" +appVersion: "2.9.3" description: Apache Pulsar Helm chart for Kuber

[GitHub] [pulsar] tisonkun added a comment to the discussion: What's the best practice to build java-test-image?

2022-07-18 Thread GitBox
GitHub user tisonkun added a comment to the discussion: What's the best practice to build java-test-image? @lhotari the next time you can answer in a different thread so that I can mark your response as the answer :) GitHub link: https://github.com/apache/pulsar/discussions/16633#discussionc

[GitHub] [pulsar] tisonkun added a comment to the discussion: What's the best practice to build java-test-image?

2022-07-18 Thread GitBox
GitHub user tisonkun added a comment to the discussion: What's the best practice to build java-test-image? The first script works! Thank you. GitHub link: https://github.com/apache/pulsar/discussions/16633#discussioncomment-3170863 This is an automatically sent email for dev@pulsar.apac

[GitHub] [pulsar] tisonkun edited a discussion: How to build java-test-image on Apple M1?

2022-07-18 Thread GitBox
GitHub user tisonkun edited a discussion: How to build java-test-image on Apple M1? cc @lhotari Confirmed as a potential improvement work. Currently, we don't support build the image on Apple M1. See also #16652 for more information. Today I'm trying to build java-test-image on Apple M1. Run

Re: [DISCUSS] PIP-180: Shadow Topic, an alternative way to support readonly topic ownership.

2022-07-18 Thread Haiting Jiang
Hi Penghui, > Can we use `message_id` directly? It's a message ID from the source > cluster, it can be used > by the shadow topic feature but can also be used by other features in the > feature. > Sure, `message_id` is better. > > there are not much difference to reset the cursor in persistent

Re: [DISCUSS] PIP-180: Shadow Topic, an alternative way to support readonly topic ownership.

2022-07-18 Thread Asaf Mesika
> > For an extra field in Command Send, as a matter of fact, there is already > an > extra field called marker introduced in Command Send to improved logic for > pausing replicated subscription snapshots when no traffic (PR #11922). I > believe it's introduced by similar reason. I looked at that

Re: PIP-187 Add API to analyse a subscription backlog and provide a accurate value

2022-07-18 Thread Nicolò Boschi
+1, good work, I think it's very valuable for users for monitoring purposes. Nicolò Boschi Il giorno lun 18 lug 2022 alle ore 11:47 Lothruin Mirwen < lothruin.mir...@gmail.com> ha scritto: > This should be really helpful to monitor real backlog in production > environments. > Currently we are s

Re: PIP-187 Add API to analyse a subscription backlog and provide a accurate value

2022-07-18 Thread Lothruin Mirwen
This should be really helpful to monitor real backlog in production environments. Currently we are struck at "entries" count but doesn't describe well how much real message lag we have. +1 excited to see it work on our production environments Diego Salvi Il giorno lun 18 lug 2022 alle ore 11:18

[GitHub] [pulsar] tisonkun added a comment to the discussion: How to build java-test-image on Apple M1?

2022-07-18 Thread GitBox
GitHub user tisonkun added a comment to the discussion: How to build java-test-image on Apple M1? It seems that upstream doesn't support Apple M1 and the dockerfile-maven-plugin has been abandon. See also https://github.com/spotify/dockerfile-maven/issues/394. It would be better to switch to

Re: PIP-187 Add API to analyse a subscription backlog and provide a accurate value

2022-07-18 Thread Enrico Olivelli
Any comments ? FYI I have updated the PIP after addressing some feedback on the PR: - no more need to create a dummy Dispatcher - now we are reading entries in batches I would like to see this in 2.11 please Enrico Il giorno gio 14 lug 2022 alle ore 09:34 Enrico Olivelli ha scritto: > > Hello,

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

2022-07-18 Thread Enrico Olivelli
Nicolò, Il Lun 18 Lug 2022, 10:00 Nicolò Boschi ha scritto: > Thanks Penghui for the reminder. > I'd like to also include PIP: 181 Pulsar shell if the time permits. > > I believe that is a good idea to start testing the code freeze proposed by > PIP-175 (https://github.com/apache/pulsar/issues/1

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

2022-07-18 Thread Nicolò Boschi
Thanks Penghui for the reminder. I'd like to also include PIP: 181 Pulsar shell if the time permits. I believe that is a good idea to start testing the code freeze proposed by PIP-175 (https://github.com/apache/pulsar/issues/15966). Even if not officially approved, we discussed it many times and a

[GitHub] [pulsar] tisonkun added a comment to the discussion: What's the best practice to build java-test-image?

2022-07-18 Thread GitBox
GitHub user tisonkun added a comment to the discussion: What's the best practice to build java-test-image? Thank you @lhotari! I'll try this script later. GitHub link: https://github.com/apache/pulsar/discussions/16633#discussioncomment-3169266 This is an automatically sent email for de

Re: [DISCUSS] Move Pulsar SQL to a separated repository?

2022-07-18 Thread Lari Hotari
Thanks for picking up this task. The decision to move Pulsar SQL out of apache/pulsar repository has been made over 2 years ago in April 2020 with PIP-62, https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories . It's not only abou