Re: Subscription

Hi Rakesh Kumar Singh, Could you please follow the link https://zookeeper.apache.org/lists.html details and I hope that will help you to subscribe ZooKeeper mailing list. Best Regards, Rakesh On Thu, Oct 6, 2016 at 11:03 AM, Rakesh Singh wrote: > Subscribing >

Subscription

Subscribing

[jira] [Commented] (BOOKKEEPER-651) Add another type of subscriber for cluster subscription

cluster Subscription based on BookKeeper 4.2.1, mainly add three features: 1/ add cluster subscription type 2/ window control for each client in cluster for flow control 3/ retry policy and re-delivery policy of cluster subscription For code view, see github: https://github.com/mocc/bookkeeper-lab

[jira] [Updated] (BOOKKEEPER-433) Validate subscriber id for subscription

[ https://issues.apache.org/jira/browse/BOOKKEEPER-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-433: - Fix Version/s: (was: 4.3.0) Validate subscriber id for subscription

[jira] [Commented] (BOOKKEEPER-433) Validate subscriber id for subscription

. Validate subscriber id for subscription --- Key: BOOKKEEPER-433 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-433 Project: Bookkeeper Issue Type: Bug Components: hedwig-server Affects

[jira] [Closed] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly closed BOOKKEEPER-369. - re-factor hedwig cpp client to provide better interface to support both one-subscription

[jira] [Closed] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly closed BOOKKEEPER-364. - re-factor hedwig java client to support both one-subscription-per-channel and multiplex

[jira] [Closed] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly closed BOOKKEEPER-252. - Hedwig: provide a subscription mode to kill other subscription channel when hedwig client

[jira] [Closed] (BOOKKEEPER-435) Create SubscriptionChannelManager to manage all subscription channel

[ https://issues.apache.org/jira/browse/BOOKKEEPER-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly closed BOOKKEEPER-435. - Create SubscriptionChannelManager to manage all subscription channel

[jira] [Updated] (BOOKKEEPER-410) Hedwig client should remove message handler while closing subscription

closing subscription -- Key: BOOKKEEPER-410 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-410 Project: Bookkeeper Issue Type: Bug Components: hedwig-client

[jira] [Updated] (BOOKKEEPER-70) reduce or multiplex subscription connections to a hub server

[ https://issues.apache.org/jira/browse/BOOKKEEPER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-70: - Fix Version/s: (was: 4.2.0) reduce or multiplex subscription connections to a hub

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

://builds.apache.org/job/bookkeeper-trunk2/24/]) BOOKKEEPER-55: SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously (sijie via ivank) (Revision 1428059) Result = SUCCESS ivank : Files : * /zookeeper

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

. SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously --- Key: BOOKKEEPER-55 URL

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

. SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously --- Key

[jira] [Comment Edited] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

lines or while lines have trailing spaces. SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

[jira] [Updated] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

could not remove all trailing spaces and long lines, since some are introduced by protobuf. BTW, I would suggest to add more detail info in the reports to indicate which line is long lines or while lines have trailing spaces. SubscribeReconnectRetryTask might retry subscription

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

at . https://builds.apache.org/job/bookkeeper-trunk-precommit-build/160/ SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

[jira] [Updated] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

, the subscriber doesn't clear its channel until it resubscribed. after that it replaced its new channel with old channel. if some one close subscription during resubscribe, when it resubscribed succeed, trying to replaced its new channel with old channel, it would find the old channel is cleared

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

at . https://builds.apache.org/job/bookkeeper-trunk-precommit-build/145/ SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

of the trailing spaces and the long line, please? SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

[jira] [Resolved] (BOOKKEEPER-410) Hedwig client should remove message handler while closing subscription

topic, final ByteString subscriberId, final CallbackResponseBody callback, final Object context) { TopicSubscriber topicSubscriber = new TopicSubscriber(topic, subscriberId); logger.debug(Stopping delivery for {} before closing subscription

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

. SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

[jira] [Resolved] (BOOKKEEPER-70) reduce or multiplex subscription connections to a hub server

[ https://issues.apache.org/jira/browse/BOOKKEEPER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly resolved BOOKKEEPER-70. -- Resolution: Implemented Assignee: Sijie Guo reduce or multiplex subscription

[jira] [Assigned] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

subscription endlessly when another subscription is already successfully created previously --- Key: BOOKKEEPER-55 URL: https

[jira] [Commented] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

reconnecting, after reconnected subscription channel needs to disconnected after succeed. otherwise, from the client side, it knew that it already closed subscription channel but actual the subscription channel is still established due to resubscribe. I think this problem already fixed in cpp client

[jira] [Updated] (BOOKKEEPER-433) Validate subscriber id for subscription

for subscription --- Key: BOOKKEEPER-433 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-433 Project: Bookkeeper Issue Type: Bug Components: hedwig-server Affects Versions: 4.2.0

[jira] [Commented] (BOOKKEEPER-410) Hedwig client should remove message handler while closing subscription

stopDelivery when closeSubscription. So I think it should already fix this issue described here. [~i0exception] Could you help double-checking about it? Hedwig client should remove message handler while closing subscription

[jira] [Resolved] (BOOKKEEPER-366) hedwig protocol changes to support multiplexing subscription channels.

BOOKKEEPER-70. hedwig protocol changes to support multiplexing subscription channels. -- Key: BOOKKEEPER-366 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-366

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

. Description --- In some case, we need to hedwig-client as proxy server to provide messaging service to other users. client - proxy server 1 - hedwig \ proxy server 2 / when client would connect to either proxy server to receive messages, the proxy server would setup subscription channel

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

subscriptions. It seems worth to clean it up, by tracking it in different data structure, and resurface it when reading subscription. Yup. Agreed. It would be cleaner as you described. - Sijie --- This is an automatically generated e-mail

[jira] [Commented] (BOOKKEEPER-435) Create SubscriptionChannelManager to manage all subscription channel

[https://builds.apache.org/job/bookkeeper-trunk/765/]) BOOKKEEPER-435: Create SubscriptionChannelManager to manage all subscription channel (sijie via ivank) (Revision 1400827) Result = UNSTABLE ivank : Files : * /zookeeper/bookkeeper/trunk/CHANGES.txt * /zookeeper/bookkeeper/trunk/hedwig

[jira] [Commented] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

[https://builds.apache.org/job/bookkeeper-trunk/759/]) BOOKKEEPER-369: re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel. (sijie via ivank) (Revision 1399578) Result = UNSTABLE ivank : Files

[jira] [Updated] (BOOKKEEPER-410) Hedwig client should remove message handler while closing subscription

subscription -- Key: BOOKKEEPER-410 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-410 Project: Bookkeeper Issue Type: Bug Components: hedwig-client, hedwig

[jira] [Created] (BOOKKEEPER-433) Validate subscriber id for subscription

Sijie Guo created BOOKKEEPER-433: Summary: Validate subscriber id for subscription Key: BOOKKEEPER-433 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-433 Project: Bookkeeper Issue

[jira] [Commented] (BOOKKEEPER-433) Validate subscriber id for subscription

way makes more sense to me (as suggested on the [other ticket|https://issues.apache.org/jira/browse/BOOKKEEPER-422?focusedCommentId=13473538page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13473538].) Validate subscriber id for subscription

[jira] [Commented] (BOOKKEEPER-433) Validate subscriber id for subscription

in ZooKeeper, if the strings has spaces or prefixing with '/', they are failed to be used as a topic name or subscriber id. so this jira would also handle such case. Validate subscriber id for subscription --- Key: BOOKKEEPER

[jira] [Created] (BOOKKEEPER-435) Create SubscriptionChannelManager to manage all subscription channel

Sijie Guo created BOOKKEEPER-435: Summary: Create SubscriptionChannelManager to manage all subscription channel Key: BOOKKEEPER-435 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-435 Project

[jira] [Updated] (BOOKKEEPER-435) Create SubscriptionChannelManager to manage all subscription channel

[ https://issues.apache.org/jira/browse/BOOKKEEPER-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-435: - Attachment: BOOKKEEPER-435.diff Attach a patch to create subscription channel manager

[jira] [Updated] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

SimpleActiveSubscriber extending from ActiveSubscriber, which doing client side throttle. re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel

[jira] [Commented] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel

[jira] [Commented] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

'enableClientThrottle' is true for simple subscription manager which only have one ActiveSubscriber alive per subscription channel. for multiplexing subscription manager, enableClientThrottle would be set to false, so no operations would take effects on the shared channel. To make the code more

[jira] [Commented] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

Running tests. Once they finish, I'll submit, assuming they all pass. re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel

Re: Review Request: BOOKKEEPER-364: re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

--- addressing Ivan' comments to move abstract things to client.netty.impl package. Description --- Currently Hedwig client is coupled with the design of one subscription per channel. In order to multiplex multiple subscription into one channel, it would be better to refine the Hedwig

[jira] [Created] (BOOKKEEPER-412) Load subscription lazily only when the subscriber creates or attaches it.

Sijie Guo created BOOKKEEPER-412: Summary: Load subscription lazily only when the subscriber creates or attaches it. Key: BOOKKEEPER-412 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-412

[jira] [Assigned] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

to support both one-subscription-per-channel and multiple-subscriptions-per-channel. Key: BOOKKEEPER-369 URL: https

[jira] [Commented] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

. re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel. -- Key: BOOKKEEPER-364

Re: Review Request: BOOKKEEPER-364: re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

--- Update a new patch addressing Ivan's comments. Description --- Currently Hedwig client is coupled with the design of one subscription per channel. In order to multiplex multiple subscription into one channel, it would be better to refine the Hedwig java client code to provide better

[jira] [Updated] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

board. re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel. -- Key: BOOKKEEPER-364

[jira] [Comment Edited] (BOOKKEEPER-410) Hedwig client should remove message handler while closing subscription

: {quote} Because of this, when a subscription request goes through with another message handler, the subscription goes fine, but we can't start delivery. The only reason for keeping the message handler is to support restartDelivery. {quote} we removed the message handler from

[jira] [Commented] (BOOKKEEPER-410) Hedwig client should remove message handler while closing subscription

a subscription request goes through with another message handler, the subscription goes fine, but we can't start delivery. The only reason for keeping the message handler is to support restartDelivery. {quote} we removed the message handler from SubscribeReconnectCallback to fix race condition on start

Re: Review Request: BOOKKEEPER-364: re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

to the interface. This isn't nice though, because it conflates the concepts of channel management and subscription management, but it's better to have a messy interface, than one that you are bypassing all the time. - Ivan Kelly On Sept. 17, 2012, 12:13 p.m., Sijie Guo wrote

Review Request: BOOKKEEPER-364: re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

is coupled with the design of one subscription per channel. In order to multiplex multiple subscription into one channel, it would be better to refine the Hedwig java client code to provide better interface to support both mode. This addresses bug BOOKKEEPER-364. https://issues.apache.org/jira

[jira] [Commented] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

/r/7129/ re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel. -- Key: BOOKKEEPER-364

[jira] [Updated] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

the abstraction for the hedwig client. so it is easy to support both one-subscription-per-channel and multiplex-subscriptions-per-channel modes. re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel

[jira] [Updated] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

, which does the same thing as java client. the patch is generated based on BOOKKEEPER-143. re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

/src/main/java/org/apache/hedwig/server/subscriptions/AbstractSubscriptionManager.java https://reviews.apache.org/r/5086/#comment24754 remove topic from topic2sub2seq. Otherwise once we disconnect the subscription channel, a client-side subscription could succeed. - Aniruddha Laud On Sept

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

, the proxy server would setup subscription channel to hedwig server. we just want client to be simple, so when the channel between client and proxy server is broken, client will try to connect to proxy servers thru VIP. it might connect to other proxy server. for example, first time client

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

- hedwig \ proxy server 2 / when client would connect to either proxy server to receive messages, the proxy server would setup subscription channel to hedwig server. we just want client to be simple, so when the channel between client and proxy server is broken, client will try to connect

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

#file154680line260 remove topic from topic2sub2seq. Otherwise once we disconnect the subscription channel, a client-side subscription could succeed. I added a flag in ReleaseOp to control whether remove topic2sub2seq or not. since StubSubscriptionManager in testing would use it, we should

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

need to hedwig-client as proxy server to provide messaging service to other users. client - proxy server 1 - hedwig \ proxy server 2 / when client would connect to either proxy server to receive messages, the proxy server would setup subscription channel to hedwig server. we just want

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

to other users. client - proxy server 1 - hedwig \ proxy server 2 / when client would connect to either proxy server to receive messages, the proxy server would setup subscription channel to hedwig server. we just want client to be simple, so when the channel between client and proxy server

[jira] [Commented] (BOOKKEEPER-402) Hedwig hub should close subscription channels on losing a topic

if we get a channel disconnected event for a subscription channel in SubscribeHandler. {code} Currently even we don't stop delivery explicitly, the active subscriber would stop delivery when encountering permanent error (channel disconnected). the only point worths to do that is to remove

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

messages, the proxy server would setup subscription channel to hedwig server. we just want client to be simple, so when the channel between client and proxy server is broken, client will try to connect to proxy servers thru VIP. it might connect to other proxy server. for example, first time client

[jira] [Commented] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

[https://builds.apache.org/job/bookkeeper-trunk/712/]) BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server. (sijie via ivank) (Revision 1384836) Result = SUCCESS ivank : Files : * /zookeeper/bookkeeper

Re: Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

--- update the patch to provide a client level subscription listener rather than a per-subscription listener. Description --- In some case, we need to hedwig-client as proxy server to provide messaging service to other users. client - proxy server 1 - hedwig \ proxy server 2 / when

[jira] [Updated] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

subscription listener rather than per-subscription listener. for now, those disable resubscribe feature subscriptions, 'TOPIC_MOVED' event will be emitted to the registered listener to notify a topic is moved when channel broken. Hedwig: provide a subscription mode to kill other

[jira] [Commented] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

://reviews.apache.org/r/5086/diff/3/ Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server

[jira] [Commented] (BOOKKEEPER-402) Hedwig hub should close subscription channels on losing a topic

()); +} topic2LocalCounts.remove(topic); notifyUnsubcribe(topic); {code} Hedwig hub should close subscription channels on losing a topic --- Key: BOOKKEEPER-402

[jira] [Commented] (BOOKKEEPER-402) Hedwig hub should close subscription channels on losing a topic

of the subscription manager was to keep the two components decoupled, the way they are right now. The subscribe handler takes care of starting and stopping deliveries as it is the one that gets events related to subscriptions. Also, we should also stop delivery if we get a channel disconnected event

[jira] [Commented] (BOOKKEEPER-402) Hedwig hub should close subscription channels on losing a topic

-75. I had a fix to close subscription channels when lostTopic, which is as part of BOOKKEEPER-252 (it also about closing subscription channels). The easy way is to call deliveryManager#stopServing in subscription manager in ReleaseTopic. since it has the subscription list for a topic, we don't

[jira] [Updated] (BOOKKEEPER-402) Hedwig hub should close subscription channels on losing a topic

and keeps the subscription channels open. It should actively close it and stop delivery for all subscribers for that topic connected to it. Reviewboard entry: https://reviews.apache.org/r/7054/ was:If a hub were to lose a topic, it doesn't stop delivery for that topic and keeps the subscription

[jira] [Commented] (BOOKKEEPER-402) Hedwig hub should close subscription channels on losing a topic

to stop delivery as a side-effect of a lost subscription and not of a lost topic. We should stop delivery only after the subscription manager is notified of the lost topic and will not accept any more subscriptions for that topic. Hedwig hub should close subscription channels

[jira] [Created] (BOOKKEEPER-402) Hedwig hub should close subscription channels on losing a topic

Aniruddha created BOOKKEEPER-402: Summary: Hedwig hub should close subscription channels on losing a topic Key: BOOKKEEPER-402 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-402 Project

Request for Apache Zookeeper mailing list subscription

Hi, I am doing my research on apache zookeeper to improve its performance. I would like to subscribe to the mailing list. Kindly, Subscribe me to the mailing list. Thanks, Dayal

[jira] [Commented] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

that disabling reconnect logic is necessary. if a subscriber subscribes with 'forceAttach', it would kill the existed attached subscription. the killed subscription would reconnect and kill the new one if we couldn't disable reconnect logic. so it would enter a killing-loop for the subscribers. after

[jira] [Commented] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

this SubscriptionChannelListener, or rather I don't like passing it to the subscribe call at least. It adds to the main subscription API and exposes the connection logic to the client in a way which has been nicely hidden up until now. Moreover, I don't think it's necessary. We have a flag

[jira] [Commented] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

passing it to the subscribe call, I think it would be better to register it with the Subscriber as a whole, if it is indeed needed. Or alternatively merge it with MessageHandler, though the problem there is that it would be a BC break. Hedwig: provide a subscription mode to kill

[jira] [Updated] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously --- Key: BOOKKEEPER-55

[jira] [Updated] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

Ivan's previous's comment. also upload to review board: https://reviews.apache.org/r/5086/ Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server

[jira] [Updated] (BOOKKEEPER-70) reduce or multiplex subscription connections to a hub server

[ https://issues.apache.org/jira/browse/BOOKKEEPER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stu Hood updated BOOKKEEPER-70: --- Summary: reduce or multiplex subscription connections to a hub server (was: reduce

[jira] [Updated] (BOOKKEEPER-332) Add SubscriptionPreferences to record all preferences for a subscription

. Add SubscriptionPreferences to record all preferences for a subscription Key: BOOKKEEPER-332 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-332 Project

[jira] [Commented] (BOOKKEEPER-332) Add SubscriptionPreferences to record all preferences for a subscription

. Add SubscriptionPreferences to record all preferences for a subscription Key: BOOKKEEPER-332 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-332 Project

[jira] [Commented] (BOOKKEEPER-332) Add SubscriptionPreferences to record all preferences for a subscription

[https://builds.apache.org/job/bookkeeper-trunk/654/]) BOOKKEEPER-332: Add SubscriptionPreferences to record all preferences for a subscription (sijie via ivank) [missing files] (Revision 1374327) BOOKKEEPER-332: Add SubscriptionPreferences to record all preferences for a subscription (sijie via

[jira] [Created] (BOOKKEEPER-369) re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel.

Sijie Guo created BOOKKEEPER-369: Summary: re-factor hedwig cpp client to provide better interface to support both one-subscription-per-channel and multiple-subscriptions-per-channel. Key: BOOKKEEPER-369 URL

[jira] [Created] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

Sijie Guo created BOOKKEEPER-364: Summary: re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel. Key: BOOKKEEPER-364 URL: https://issues.apache.org

[jira] [Updated] (BOOKKEEPER-364) re-factor hedwig java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel.

java client to support both one-subscription-per-channel and multiplex-subscriptions-per-channel. -- Key: BOOKKEEPER-364 URL: https

[jira] [Updated] (BOOKKEEPER-332) Add SubscriptionPreferences to record all preferences for a subscription

and BOOKKEEPER-338, which removes backward compatible related staffs after BOOKKEEPER-340 is in. please review BOOKKEEPER-283, BOOKKEEPER-338 and this one in order. Add SubscriptionPreferences to record all preferences for a subscription

[jira] [Updated] (BOOKKEEPER-332) Add SubscriptionPreferences to record all preferences for a subscription

[ https://issues.apache.org/jira/browse/BOOKKEEPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-332: - Attachment: BOOKKEEPER-332.patch add subscription preferences in subscription data. it did

[jira] [Created] (BOOKKEEPER-332) Add SubscriptionPreferences to record all preferences for a subscription

Sijie Guo created BOOKKEEPER-332: Summary: Add SubscriptionPreferences to record all preferences for a subscription Key: BOOKKEEPER-332 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-332

[jira] [Commented] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server. -- Key: BOOKKEEPER-252 URL

[jira] [Comment Edited] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

: --- attach a patch based on latest trunk. the patch is generated based on BOOKKEEPER-191. was (Author: hustlmsp): attach a patch based on latest trunk. Hedwig: provide a subscription mode to kill other subscription channel when hedwig client

[jira] [Updated] (BOOKKEEPER-70) reduce or demultiplex subscription connections to a hub server

[ https://issues.apache.org/jira/browse/BOOKKEEPER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-70: Fix Version/s: 4.2.0 reduce or demultiplex subscription connections to a hub server

Review Request: BOOKKEEPER-252: Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

-client as proxy server to provide messaging service to other users. client - proxy server 1 - hedwig \ proxy server 2 / when client would connect to either proxy server to receive messages, the proxy server would setup subscription channel to hedwig server. we just want client to be simple, so

[jira] [Commented] (BOOKKEEPER-252) Hedwig: provide a subscription mode to kill other subscription channel when hedwig client is used as a proxy-style server.

-client as proxy server to provide messaging service to other users. client - proxy server 1 - hedwig \ proxy server 2 / when client would connect to either proxy server to receive messages, the proxy server would setup subscription channel to hedwig server. we just want client to be simple, so

[jira] [Updated] (BOOKKEEPER-55) SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

. SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously

[jira] [Commented] (BOOKKEEPER-133) Hub server should update subscription state to zookeeper when losing topic or shutting down

[https://builds.apache.org/job/bookkeeper-trunk/291/]) BOOKKEEPER-133: Hub server should update subscription state to zookeeper when losing topic or shutting down (Sijie Gou via ivank) ivank : Files : * /zookeeper/bookkeeper/trunk/CHANGES.txt * /zookeeper/bookkeeper/trunk/hedwig-server/src/main

[jira] [Commented] (BOOKKEEPER-133) Hub server should update subscription state to zookeeper when losing topic or shutting down

is null, so you're not really extracting out common code at all. Also, when you upload these changes, could you put them in reviewboard. Hub server should update subscription state to zookeeper when losing topic or shutting down

[jira] [Commented] (BOOKKEEPER-133) Hub server should update subscription state to zookeeper when losing topic or shutting down

. Hub server should update subscription state to zookeeper when losing topic or shutting down --- Key: BOOKKEEPER-133 URL: https://issues.apache.org/jira/browse

[jira] [Commented] (BOOKKEEPER-133) Hub server should update subscription state to zookeeper when losing topic or shutting down

-based mechanism to update subscription state lazily to zookeeper. But in the following case, it didn't do it. 1) losing ownership of Topic 2) hub server shuts down This addresses bug BOOKKEEPER-133. https://issues.apache.org/jira/browse/BOOKKEEPER-133 Diffs - hedwig-server/src/main

[jira] [Updated] (BOOKKEEPER-133) Hub server should update subscription state to zookeeper when losing topic or shutting down

sending consume request when closing subscription. since close subscription will be called when a channel is disconnected. so client can't send a consume request thru a unconnected channel. It would be better to let application handle how to consume. Hub server should update

  1   2   >