You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/05/22 18:52:04 UTC

[jira] [Updated] (SENTRY-1778) Close query as soon as it is done

     [ https://issues.apache.org/jira/browse/SENTRY-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Na Li updated SENTRY-1778:
--------------------------
    Description: 
Make sure we close all query results after we have finished with them. Failure to do so will result in significant memory leaks in your application.  mentioned in http://www.datanucleus.org/products/accessplatform_4_1/jdo/performance_tuning.html

Since we always close the transaction, and closing transaction will close the query, the memory leak without this change should not be significant. This is why this issue is not high priority. On the other hand, closing query result sooner should not have side effect.

  was:Make sure we close all query results after we have finished with them. Failure to do so will result in significant memory leaks in your application.  mentioned in http://www.datanucleus.org/products/accessplatform_4_1/jdo/performance_tuning.html


> Close query as soon as it is done
> ---------------------------------
>
>                 Key: SENTRY-1778
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1778
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Na Li
>            Assignee: Na Li
>            Priority: Minor
>             Fix For: sentry-ha-redesign
>
>
> Make sure we close all query results after we have finished with them. Failure to do so will result in significant memory leaks in your application.  mentioned in http://www.datanucleus.org/products/accessplatform_4_1/jdo/performance_tuning.html
> Since we always close the transaction, and closing transaction will close the query, the memory leak without this change should not be significant. This is why this issue is not high priority. On the other hand, closing query result sooner should not have side effect.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)