portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-1090) Jetspeed 2.1 derby database becoming huge.
Date Thu, 28 Jan 2010 19:47:34 GMT

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

David Sean Taylor resolved JS2-1090.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.1.1-RC)
                   2.2.1
         Assignee: David Sean Taylor

> Jetspeed 2.1 derby database becoming huge.
> ------------------------------------------
>
>                 Key: JS2-1090
>                 URL: https://issues.apache.org/jira/browse/JS2-1090
>             Project: Jetspeed 2
>          Issue Type: Task
>    Affects Versions: 2.1.1-RC
>         Environment: Windows 2003 SP2
>            Reporter: Nishant Malviya
>            Assignee: David Sean Taylor
>             Fix For: 2.2.1
>
>
> The customer has 2 portlet applications. one with 36 portlets and the second one with
only 1 portlet. The customer is complaining that there are a couple .dat files that are taking
up a large amount of space:
>  ...jetspeed\2.1\database\derby\productiondb\seg0:
> c3c0.dat (12.5 GB)
> c3d0.dat (8.78 GB)
> There are 283 other *.dat files in the same folder of much smaller size. Does this amount
of space seem reasonable for the amount of deployed portlets?  Is there any way to reduce
this size?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message