db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6105) Implement resource constraints for Derby.
Date Tue, 25 Jun 2013 04:38:20 GMT

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

Mamta A. Satoor updated DERBY-6105:

    Urgency: Normal
     Labels: derby_triage10_11  (was: )
> Implement resource constraints for Derby.
> -----------------------------------------
>                 Key: DERBY-6105
>                 URL: https://issues.apache.org/jira/browse/DERBY-6105
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, Store
>    Affects Versions:
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_11
> Resource constraints could help protect Derby from denial-of-service attacks. Resource
constraints would be useful for throttling runaway users or enforcing quota licenses in multi-tenant
situations, i.e., where an installation simultaneously runs multiple instances of the same
application or several different applications. Resource constraints are discussed in the following
email thread: http://apache-database.10148.n7.nabble.com/How-to-limit-Derby-size-on-Disk-td127797.html
> The following file system constraints might be interesting:
> 1) Limits on the total space consumed by a database.
> 2) Limits on the total space consumed by an individual table.
> 3) Limits on the number of rows in an individual table.
> 4) Limits on the total space consumed by all tables owned by a given user or role. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message