[DISCUSS] Pulsar release

(Starting a new thread to detach from the general website discussion) I think that it would be good to try to release a new Pulsar version ASAP, following the Apache release process and requirements. That would take the project out of the current limbo where we are in the incubator, but we can on

Re: Pulsar web site is online!

Hi Matteo, > On Jul 21, 2017, at 2:55 PM, Matteo Merli wrote: > > Hi Dave, > > sorry for late reply No concerns. > >> You might take a look at https://www.apache.org/foundation/marks/linking > > I went through this and so far we don't have any external links / logos. Is > there any specific

Re: Pulsar web site is online!

Hi Dave, sorry for late reply > You might take a look at https://www.apache.org/foundation/marks/linking I went through this and so far we don't have any external links / logos. Is there any specific point you were thinking about? > There are links to GitHub.com/yahoo/pulsar

[GitHub] merlimat closed pull request #588: clear up pendingReceive queue when consumer close

merlimat closed pull request #588: clear up pendingReceive queue when consumer close URL: https://github.com/apache/incubator-pulsar/pull/588 This is an automated message from the Apache Git Service. To respond to the messa

[GitHub] merlimat commented on a change in pull request #574: Documentation changes (work in progress)

merlimat commented on a change in pull request #574: Documentation changes (work in progress) URL: https://github.com/apache/incubator-pulsar/pull/574#discussion_r128868516 ## File path: site/_data/sidebar.yaml ## @@ -91,6 +88,14 @@ groups: - title: Codebase endpoi

[GitHub] merlimat commented on a change in pull request #574: Documentation changes (work in progress)

merlimat commented on a change in pull request #574: Documentation changes (work in progress) URL: https://github.com/apache/incubator-pulsar/pull/574#discussion_r128867363 ## File path: site/_data/sidebar.yaml ## @@ -91,6 +88,14 @@ groups: - title: Codebase endpoi

[GitHub] merlimat commented on a change in pull request #574: Documentation changes (work in progress)

merlimat commented on a change in pull request #574: Documentation changes (work in progress) URL: https://github.com/apache/incubator-pulsar/pull/574#discussion_r128865784 ## File path: site/_data/sidebar.yaml ## @@ -91,6 +88,14 @@ groups: - title: Codebase endpoi

[GitHub] merlimat commented on a change in pull request #574: Documentation changes (work in progress)

merlimat commented on a change in pull request #574: Documentation changes (work in progress) URL: https://github.com/apache/incubator-pulsar/pull/574#discussion_r128867045 ## File path: site/docs/latest/advanced/PartitionedTopics.md ## @@ -0,0 +1,88 @@ +--- +title: Partit

[GitHub] merlimat commented on a change in pull request #574: Documentation changes (work in progress)

merlimat commented on a change in pull request #574: Documentation changes (work in progress) URL: https://github.com/apache/incubator-pulsar/pull/574#discussion_r128866606 ## File path: site/_data/sidebar.yaml ## @@ -91,6 +88,14 @@ groups: - title: Codebase endpoi

[GitHub] lucperkins commented on a change in pull request #574: Documentation changes (work in progress)

lucperkins commented on a change in pull request #574: Documentation changes (work in progress) URL: https://github.com/apache/incubator-pulsar/pull/574#discussion_r128866126 ## File path: site/_data/sidebar.yaml ## @@ -35,14 +35,11 @@ groups: endpoint: InstanceSetup

[GitHub] merlimat commented on a change in pull request #574: Documentation changes (work in progress)

merlimat commented on a change in pull request #574: Documentation changes (work in progress) URL: https://github.com/apache/incubator-pulsar/pull/574#discussion_r128865398 ## File path: site/_data/sidebar.yaml ## @@ -35,14 +35,11 @@ groups: endpoint: InstanceSetup

[GitHub] merlimat commented on issue #402: Rate limiting in the dispatcher

merlimat commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317114926 > r. So, ideally if broker becomes busy, load manager should shed load to bring down its load. Yes, but that might happen later. In

[GitHub] saandrews commented on issue #402: Rate limiting in the dispatcher

saandrews commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317114449 I had the same point, but the broker resource related load balancing is done by load manager. So, ideally if broker becomes busy, load mana

[GitHub] rdhabalia commented on issue #402: Rate limiting in the dispatcher

rdhabalia commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317110810 > I was talking at the ManagedLedger level cache Yes. I think then we do not throttle already caught up consumers ([activeCursors](htt

[GitHub] rdhabalia commented on issue #402: Rate limiting in the dispatcher

rdhabalia commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317109262 > That would be to ensure the broker resources are not exceeded. When that happens, delivery will be slowed down Also, it would be interes

[GitHub] merlimat commented on issue #402: Rate limiting in the dispatcher

merlimat commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317107464 > Yes, actually earlier in the PIP I have defined Broker level configuration rather Cluster level configuration but team decided to go with Cl

[GitHub] rdhabalia commented on issue #402: Rate limiting in the dispatcher

rdhabalia commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317106846 > think that if the objective is to protect broker, another approach would be to a have a per-broker limit. When the limit is reached, the t

[GitHub] merlimat commented on issue #402: Rate limiting in the dispatcher

merlimat commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317106616 > broker needs visibility of bookie's caching I was talking at the ManagedLedger level cache -

[GitHub] rdhabalia commented on issue #402: Rate limiting in the dispatcher

rdhabalia commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317104964 >Can you add information on the implementation approach? Sure, I will broker changes details. > Another thought, should we diff

[GitHub] merlimat closed pull request #589: Updated README by removing broken links and adding instruction on how to build

merlimat closed pull request #589: Updated README by removing broken links and adding instruction on how to build URL: https://github.com/apache/incubator-pulsar/pull/589 This is an automated message from the Apache Git Ser

[GitHub] merlimat commented on a change in pull request #543: Added documents for wildcard matching in authorization

merlimat commented on a change in pull request #543: Added documents for wildcard matching in authorization URL: https://github.com/apache/incubator-pulsar/pull/543#discussion_r128844951 ## File path: site/_includes/explanations/permissions.md ## @@ -14,6 +14,37 @@ $ pulsa

[GitHub] merlimat commented on issue #402: Rate limiting in the dispatcher

merlimat commented on issue #402: Rate limiting in the dispatcher URL: https://github.com/apache/incubator-pulsar/issues/402#issuecomment-317092503 @rdhabalia Can you add information on the implementation approach? How is the limit going to be enforced? In all the cases, global-lim

[GitHub] merlimat opened a new pull request #589: Updated README by removing broken links and adding instruction on how to build

merlimat opened a new pull request #589: Updated README by removing broken links and adding instruction on how to build URL: https://github.com/apache/incubator-pulsar/pull/589 ### Motivation Fixed broken links on top-level README file --

Re: Github documentation links

Yes, the README.md in root directory needs to be updated to point to the website. It couldn't be done in the same commit, because it took time to get the website online after the commit. I'm changing it right now, and I'll also add basic info on how to build from source, since the README is what

Github documentation links

Did we link our GitHub page "Documentation" section to the new website or is it still work in progress? They are returning 404. e.g: https://github.com/apache/incubator-pulsar/blob/master/docs/Documentation.md

[GitHub] merlimat closed pull request #587: Upgrade to RocksDB 5.5.5 with Apache License 2.0

merlimat closed pull request #587: Upgrade to RocksDB 5.5.5 with Apache License 2.0 URL: https://github.com/apache/incubator-pulsar/pull/587 This is an automated message from the Apache Git Service. To respond to the messag