You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Tsuyoshi Ito (JIRA)" <ji...@apache.org> on 2011/02/22 15:46:43 UTC
[jira] Created: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
-----------------------------------------------------------------------------------------------------------
Key: CLEREZZA-432
URL: https://issues.apache.org/jira/browse/CLEREZZA-432
Project: Clerezza
Issue Type: Bug
Reporter: Tsuyoshi Ito
Assignee: Reto Bachmann-Gmür
Priority: Critical
http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
In our case one web-resources-cache is 192MB (operating system: windows 7).
Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Tsuyoshi Ito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997893#comment-12997893 ]
Tsuyoshi Ito commented on CLEREZZA-432:
---------------------------------------
IMO the critical issue issue is that each time I start the platform 2x web-resources-cache.graph is generated.
Starting 2x => 4 web-resources-cache.graph s - doesn't matter if I shutdown correctly or not.
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "franco fallica (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000150#comment-13000150 ]
franco fallica commented on CLEREZZA-432:
-----------------------------------------
Just to show you that this issue is important: My story of this morning.
On Friday night one of our clerezza instance went down (planed) for backup. It came backup after the backup ended successfully, but it was never reachable over the web because it has always thrown a "too many open files exception" coming from the storageProvider. Even I am aware of this issue it still took me 30 min to find out that this was because of the cached webresource graphs.
In the end the result of this issue was that this particular clerezza instance was down (meaning not usable by the customer) for about 55 hours !
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Tsuyoshi Ito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997859#comment-12997859 ]
Tsuyoshi Ito commented on CLEREZZA-432:
---------------------------------------
thanks for the explanation. IMO it is not necessary to automatize the removing process.
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "franco fallica (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997870#comment-12997870 ]
franco fallica commented on CLEREZZA-432:
-----------------------------------------
IMO it's necessary to automatically delete unused cache graphs. Because, if in a production environment clerezza crashes, it's to easy to forget deleting these folders and then eventually you run into disk space problems you would not have otherwise.
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000238#comment-13000238 ]
Henry Story commented on CLEREZZA-432:
--------------------------------------
If one added information to a special graph that keeps information about where graphs come from, their e-tags and their validity dates, one could then even remove all graphs that were out of date. In any case this would be very useful for other tasks, to reduce fetching graphs
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Tsuyoshi Ito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997868#comment-12997868 ]
Tsuyoshi Ito commented on CLEREZZA-432:
---------------------------------------
I tested again:
Start clerezza: a new web-resources-cache.graph will be generated.
Shutdown clerezza a new web-resources-cache.graph will be generated
Futhermore during shutting down the platform 2-3 web-resources-cache.graph will be generated and deleted
=> each time I start the platform 2 new web-resources-cache.graph are generated
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997884#comment-12997884 ]
Reto Bachmann-Gmür commented on CLEREZZA-432:
---------------------------------------------
@Franco: ok, I might look at it, but I have some higher priorities, a patch would be very welcome
@Tsuy: I think this could be avoided by having the content.fsadaptor bundle with a higher runlevel, otherwise this bundle is very busy during shutdown, as it removes bundle-provided web-resources whenever a bundle is stopped
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Tsuyoshi Ito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999341#comment-12999341 ]
Tsuyoshi Ito commented on CLEREZZA-432:
---------------------------------------
Tested under windows 7:
Each time a bundle is updated a new http://zz.localhost/web-resources.graph is created.
Old http://zz.localhost/web-resources.graph Graphs were never deleted
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Tsuyoshi Ito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998938#comment-12998938 ]
Tsuyoshi Ito commented on CLEREZZA-432:
---------------------------------------
While shutting down the platform the BundleFsLoader is not able to delete the temporary graph because weightedTcProviders are already deactived. therefore tcmanager can not retrieve the graph => no such entity exception
is the following workaround applicable: when activating the BundleFsLoader all web-resource.graphs are deleted
protected def activate(context: ComponentContext) {
synchronized {
for(mGraphUri <- tcManager.listMGraphs) {
if(mGraphUri.getUnicodeString.contains("http://zz.localhost/web-resources")) {
tcManager.deleteTripleCollection(mGraphUri);
}
}
...
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CLEREZZA-432) when starting clerezza platform a new
web-resources-cache.graph will be created with timestamp in file name
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür closed CLEREZZA-432.
---------------------------------------
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997855#comment-12997855 ]
Reto Bachmann-Gmür commented on CLEREZZA-432:
---------------------------------------------
There should never be more than two of these at a point in time, the reason for this is that when new files (web-resources) are available a new cache-graph is created and while this happens requests are still forwarded to the old cache-graph. If improper shutdown may cause old cache-graphs not to be properly removed, in this case the graphs can be remove manually. Should this be automatized?
An issue is however that the permissons for the old caches are still in http://zz.localhost/graph-access.graph, I've created CLEREZZA-433 to fix this.
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (CLEREZZA-432) when starting clerezza
platform a new web-resources-cache.graph will be created with timestamp in
file name
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997855#comment-12997855 ]
Reto Bachmann-Gmür edited comment on CLEREZZA-432 at 2/22/11 3:37 PM:
----------------------------------------------------------------------
There should never be more than two of these at a point in time, the reason for this is that when new files (web-resources) are available a new cache-graph is created and while this happens requests are still forwarded to the old cache-graph. Improper shutdown may cause old cache-graphs not to be properly removed, in this case the graphs can be remove manually. Should this be automatized?
An issue is however that the permissons for the old caches are still in http://zz.localhost/graph-access.graph, I've created CLEREZZA-433 to fix this.
was (Author: reto):
There should never be more than two of these at a point in time, the reason for this is that when new files (web-resources) are available a new cache-graph is created and while this happens requests are still forwarded to the old cache-graph. If improper shutdown may cause old cache-graphs not to be properly removed, in this case the graphs can be remove manually. Should this be automatized?
An issue is however that the permissons for the old caches are still in http://zz.localhost/graph-access.graph, I've created CLEREZZA-433 to fix this.
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (CLEREZZA-432) when starting clerezza platform a
new web-resources-cache.graph will be created with timestamp in file name
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür resolved CLEREZZA-432.
-----------------------------------------
Resolution: Fixed
I could not reproduce the problem on cache-grap being added (without the old one being deleted) when a bundle is update.
Applied the fix suggested by Tsuy for old cache to be removed on activation.
> when starting clerezza platform a new web-resources-cache.graph will be created with timestamp in file name
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-432
> URL: https://issues.apache.org/jira/browse/CLEREZZA-432
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298384804817
> http%3A%2F%2Fzz.localhost%2Fweb-resources-cache.graph1298369686808
> In our case one web-resources-cache is 192MB (operating system: windows 7).
> Disc space is not expensive but I am wondering why this is necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira