It’s available through REST and Admin Java API. https://pulsar.apache.org/api/admin/
The call applies to all the topics for a namespace, but it’s not possible to modify multiple namespaces in a single call. On Thu, May 9, 2019 at 11:56 AM Enrico Olivelli <eolive...@gmail.com> wrote: > Il gio 9 mag 2019, 18:44 Matteo Merli <matteo.me...@gmail.com> ha scritto: > > > Hi Enrico, > > > > that's the default setting for the broker. You can also dynamically > > override the setting for a particular namespace. > > eg.: > > > > bin/pulsar-admin namespaces set-persistence \ > > public/default \ > > --bookkeeper-ensemble 3 \ > > --bookkeeper-write-quorum 3 \ > > --bookkeeper-ack-quorum 2 \ > > --ml-mark-delete-max-rate 1.0 > > > > The change is automatically applied to new ledgers at the next ledger > > rollover. > > (You can also force a rollover by reloading the topic: pulsar-admin > > topics unload $TOPIC ) > > > > > Interesting. Is this available from Java API? > Is it possible to apply the change to multiple topics/namespaces with one > call? > Thanks Matteo > > Enrico > > > > On Wed, May 8, 2019 at 11:45 PM Enrico Olivelli <eolive...@gmail.com> > > wrote: > > > > > > Hi, > > > I am launching Pulsar Broker inside the process of my application. > > > > > > I would like to change the replication factor of ledgers dynamically > > > without restating the broker. > > > > > > I have taken a look at code and it seems to me that if I use > > > > > > org.apache.pulsar.broker.ServiceConfiguration#setManagedLedgerDefaultEnsembleSize > > > on the original ServerConfiguration I have passed to the constructor of > > > "PulsarService" > > > the new value will be eventually picked up for new "managed ledgers". > > > > > > I know this is an unsupported feature, but do you guys think it can > > really > > > work ? > > > > > > Regards > > > Enrico > > > -- -- Matteo Merli <matteo.me...@gmail.com>
