Re: python plasma client get_buffers behavior
sorry typo in above email . So I have to call del python_object to make sure that underlying PlasmaBuffer is released from plasma so that the release from plasma is not delayed till the python_object is reinitialised until the next iteration of poll loop. On Thu, Jun 11, 2020 at 8:49 PM saurabh pratap singh < saurabh.cs...@gmail.com> wrote: > Figured it out I have to call del obj to make sure the underlying > PlasmaBuffer is called. > > On Wed, Jun 10, 2020 at 9:17 PM saurabh pratap singh < > saurabh.cs...@gmail.com> wrote: > >> Hi >> >> We are using python plasma client to do a get_buffers for arrow tables >> created by java in plasma . >> >> The python plasma client basically polls on a queue and do a get_buffers >> on the object ids returned from the queue. >> What I have observed is tin context of plasma object table entry for >> those object ids is that the get_buffers will first increment the ref count >> by 1 and then there is an implicit release call which decreases the ref >> count again . >> >> But when there are no more entries in the queue I see that few object ids >> still have a lingering reference count in plasma wrt to get_buffers and >> there was no "implicit" release for that get call like previous one. >> >> Is this expected ? >> Is there any way I can handle this and make and explicit release for such >> object ids as well . >> >> Thanks >> >
Re: python plasma client get_buffers behavior
Figured it out I have to call del obj to make sure the underlying PlasmaBuffer is called. On Wed, Jun 10, 2020 at 9:17 PM saurabh pratap singh < saurabh.cs...@gmail.com> wrote: > Hi > > We are using python plasma client to do a get_buffers for arrow tables > created by java in plasma . > > The python plasma client basically polls on a queue and do a get_buffers > on the object ids returned from the queue. > What I have observed is tin context of plasma object table entry for those > object ids is that the get_buffers will first increment the ref count by 1 > and then there is an implicit release call which decreases the ref count > again . > > But when there are no more entries in the queue I see that few object ids > still have a lingering reference count in plasma wrt to get_buffers and > there was no "implicit" release for that get call like previous one. > > Is this expected ? > Is there any way I can handle this and make and explicit release for such > object ids as well . > > Thanks >
python plasma client get_buffers behavior
Hi We are using python plasma client to do a get_buffers for arrow tables created by java in plasma . The python plasma client basically polls on a queue and do a get_buffers on the object ids returned from the queue. What I have observed is tin context of plasma object table entry for those object ids is that the get_buffers will first increment the ref count by 1 and then there is an implicit release call which decreases the ref count again . But when there are no more entries in the queue I see that few object ids still have a lingering reference count in plasma wrt to get_buffers and there was no "implicit" release for that get call like previous one. Is this expected ? Is there any way I can handle this and make and explicit release for such object ids as well . Thanks
