[jira] [Updated] (ARROW-2551) [Plasma] Improve notification related code
[ https://issues.apache.org/jira/browse/ARROW-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijun Fu updated ARROW-2551: - Description: There are two issues in current Plasma notification code > [Plasma] Improve notification related code > -- > > Key: ARROW-2551 > URL: https://issues.apache.org/jira/browse/ARROW-2551 > Project: Apache Arrow > Issue Type: Improvement > Components: Plasma (C++) >Reporter: Zhijun Fu >Priority: Minor > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > There are two issues in current Plasma notification code -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARROW-2551) [Plasma] Improve notification related code
[ https://issues.apache.org/jira/browse/ARROW-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijun Fu updated ARROW-2551: - Description: (was: https://github.com/apache/arrow/pull/2011 This change addresses two issues in plasma notification code: # Currently plasma store uses recv_fd to receive the notification fd from client. As mentioned in comments from the code, this could cause plasma store to hang if client doesn't call send_fd. This particular change puts the notification fd in SubscriptionRequest to solve the problem. # When a client subscribes to plasma store, the store pushes notifications of existing objects to ALL subscribers - while in this case it just needs to push to the new subscriber. This change adds a new interface to push to a particular client.) > [Plasma] Improve notification related code > -- > > Key: ARROW-2551 > URL: https://issues.apache.org/jira/browse/ARROW-2551 > Project: Apache Arrow > Issue Type: Improvement > Components: Plasma (C++) >Reporter: Zhijun Fu >Priority: Minor > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARROW-2551) [Plasma] Improve notification related code
[ https://issues.apache.org/jira/browse/ARROW-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijun Fu updated ARROW-2551: - Description: https://github.com/apache/arrow/pull/2011 This change addresses two issues in plasma notification code: # Currently plasma store uses recv_fd to receive the notification fd from client. As mentioned in comments from the code, this could cause plasma store to hang if client doesn't call send_fd. This particular change puts the notification fd in SubscriptionRequest to solve the problem. # When a client subscribes to plasma store, the store pushes notifications of existing objects to ALL subscribers - while in this case it just needs to push to the new subscriber. This change adds a new interface to push to a particular client. was: This change addresses two issues in plasma notification code: # Currently plasma store uses recv_fd to receive the notification fd from client. As mentioned in comments from the code, this could cause plasma store to hang if client doesn't call send_fd. This particular change puts the notification fd in SubscriptionRequest to solve the problem. # When a client subscribes to plasma store, the store pushes notifications of existing objects to ALL subscribers - while in this case it just needs to push to the new subscriber. This change adds a new interface to push to a particular client. > [Plasma] Improve notification related code > -- > > Key: ARROW-2551 > URL: https://issues.apache.org/jira/browse/ARROW-2551 > Project: Apache Arrow > Issue Type: Improvement > Components: Plasma (C++) >Reporter: Zhijun Fu >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > https://github.com/apache/arrow/pull/2011 > This change addresses two issues in plasma notification code: > # Currently plasma store uses recv_fd to receive the notification fd from > client. As mentioned in comments from the code, this could cause plasma store > to hang if client doesn't call send_fd. This particular change puts the > notification fd in SubscriptionRequest to solve the problem. > # When a client subscribes to plasma store, the store pushes notifications > of existing objects to ALL subscribers - while in this case it just needs to > push to the new subscriber. This change adds a new interface to push to a > particular client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARROW-2551) [Plasma] Improve notification related code
[ https://issues.apache.org/jira/browse/ARROW-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ARROW-2551: -- Labels: pull-request-available (was: ) > [Plasma] Improve notification related code > -- > > Key: ARROW-2551 > URL: https://issues.apache.org/jira/browse/ARROW-2551 > Project: Apache Arrow > Issue Type: Improvement > Components: Plasma (C++) >Reporter: Zhijun Fu >Priority: Minor > Labels: pull-request-available > > This change addresses two issues in plasma notification code: > # Currently plasma store uses recv_fd to receive the notification fd from > client. As mentioned in comments from the code, this could cause plasma store > to hang if client doesn't call send_fd. This particular change puts the > notification fd in SubscriptionRequest to solve the problem. > # When a client subscribes to plasma store, the store pushes notifications > of existing objects to ALL subscribers - while in this case it just needs to > push to the new subscriber. This change adds a new interface to push to a > particular client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
