[jira] [Resolved] (JENA-1612) TDB2 Loader Plan for large data/constrained RAM.

2018-10-11 Thread Andy Seaborne (JIRA)


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

Andy Seaborne resolved JENA-1612.
-
Resolution: Done

> TDB2 Loader Plan for large data/constrained RAM.
> 
>
> Key: JENA-1612
> URL: https://issues.apache.org/jira/browse/JENA-1612
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: TDB2
>Affects Versions: Jena 3.9.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.10.0
>
>
> This adds an expeirmental loaded plan that is between purely sequential and 
> parallel schemes (phased or fully parallel). It may improve performance when 
> index size is larger than available RAM.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1612) TDB2 Loader Plan for large data/constrained RAM.

2018-10-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/JENA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646739#comment-16646739
 ] 

ASF GitHub Bot commented on JENA-1612:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/478


> TDB2 Loader Plan for large data/constrained RAM.
> 
>
> Key: JENA-1612
> URL: https://issues.apache.org/jira/browse/JENA-1612
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: TDB2
>Affects Versions: Jena 3.9.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.10.0
>
>
> This adds an expeirmental loaded plan that is between purely sequential and 
> parallel schemes (phased or fully parallel). It may improve performance when 
> index size is larger than available RAM.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena pull request #478: JENA-1612: A lightly parallel loader plan.

2018-10-11 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/478


---


[jira] [Resolved] (JENA-1617) dead link in Javadoc menu for Fuseki

2018-10-11 Thread Andy Seaborne (JIRA)


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

Andy Seaborne resolved JENA-1617.
-
   Resolution: Done
 Assignee: Andy Seaborne
Fix Version/s: Jena 3.9.0

> dead link in Javadoc menu for Fuseki
> 
>
> Key: JENA-1617
> URL: https://issues.apache.org/jira/browse/JENA-1617
> Project: Apache Jena
>  Issue Type: Documentation
>  Components: Documentation
>Affects Versions: Jena 3.9.0
>Reporter: Elie Roux
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.9.0
>
>
> On [https://jena.apache.org/] I click on the "Javadoc" dropdown menu at the 
> top, then click "Fuseki", it leads me to 
> [https://jena.apache.org/documentation/javadoc/fuseki/] which is a 404



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JENA-1617) dead link in Javadoc menu for Fuseki

2018-10-11 Thread Andy Seaborne (JIRA)


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

Andy Seaborne closed JENA-1617.
---

> dead link in Javadoc menu for Fuseki
> 
>
> Key: JENA-1617
> URL: https://issues.apache.org/jira/browse/JENA-1617
> Project: Apache Jena
>  Issue Type: Documentation
>  Components: Documentation
>Affects Versions: Jena 3.9.0
>Reporter: Elie Roux
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.9.0
>
>
> On [https://jena.apache.org/] I click on the "Javadoc" dropdown menu at the 
> top, then click "Fuseki", it leads me to 
> [https://jena.apache.org/documentation/javadoc/fuseki/] which is a 404



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1617) dead link in Javadoc menu for Fuseki

2018-10-11 Thread Andy Seaborne (JIRA)


[ 
https://issues.apache.org/jira/browse/JENA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646369#comment-16646369
 ] 

Andy Seaborne commented on JENA-1617:
-

Thanks. Should now be fixed.

 

It looks right on jena.staging.apache.org and I re-published the website. 
(Caching may mean it takes a while to show up on the published site.)

> dead link in Javadoc menu for Fuseki
> 
>
> Key: JENA-1617
> URL: https://issues.apache.org/jira/browse/JENA-1617
> Project: Apache Jena
>  Issue Type: Documentation
>  Components: Documentation
>Affects Versions: Jena 3.9.0
>Reporter: Elie Roux
>Priority: Major
>
> On [https://jena.apache.org/] I click on the "Javadoc" dropdown menu at the 
> top, then click "Fuseki", it leads me to 
> [https://jena.apache.org/documentation/javadoc/fuseki/] which is a 404



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1617) dead link in Javadoc menu for Fuseki

2018-10-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/JENA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646361#comment-16646361
 ] 

ASF subversion and git services commented on JENA-1617:
---

Commit 1843544 from [~an...@apache.org] in branch 'site/trunk'
[ https://svn.apache.org/r1843544 ]

JENA-1617: Fix link to Fuseki javadoc

> dead link in Javadoc menu for Fuseki
> 
>
> Key: JENA-1617
> URL: https://issues.apache.org/jira/browse/JENA-1617
> Project: Apache Jena
>  Issue Type: Documentation
>  Components: Documentation
>Affects Versions: Jena 3.9.0
>Reporter: Elie Roux
>Priority: Major
>
> On [https://jena.apache.org/] I click on the "Javadoc" dropdown menu at the 
> top, then click "Fuseki", it leads me to 
> [https://jena.apache.org/documentation/javadoc/fuseki/] which is a 404



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena pull request #481: JENA-1615 - Compaction leaks file descriptors

2018-10-11 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/481


---


[jira] [Commented] (JENA-1615) Compaction leaks file descriptors

2018-10-11 Thread Andy Seaborne (JIRA)


[ 
https://issues.apache.org/jira/browse/JENA-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646353#comment-16646353
 ] 

Andy Seaborne commented on JENA-1615:
-

Thanks for the confirmation, it's very helpful to have independent verification 
- I'll merge the PR.

> Compaction leaks file descriptors
> -
>
> Key: JENA-1615
> URL: https://issues.apache.org/jira/browse/JENA-1615
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Core, TDB2
>Affects Versions: Jena 3.8.0
> Environment: I reproduced the issue on the following environments:
>  * OS / Java:
>  ** MacOS 10.13.5
> Java 1.8.0_161 (Oracle)
>  ** Debian 9.5
> Java 1.8.0_181 (OpenJDK)
>  * Jena version 3.8.0
>  * TDB2 mode: mapped
>Reporter: Damien Obrist
>Priority: Major
> Attachments: open_files_after_compaction_after_gc.png, 
> open_files_after_compaction_after_gc_with_fix.png, 
> open_files_after_compaction_before_gc.png, open_files_before_compaction.png
>
>
> h3. Context
> I'm using a TDB2 dataset in a long-running Scala application, in which the 
> dataset gets compacted regularly. After compactions, the application removes 
> the {{Data-}} folder of the previous generation. However, the 
> corresponding disk space isn't properly returned back to the OS, but is still 
> reported as being used by {{df}}. Indeed, {{lsof}} shows that the application 
> keeps open file descriptors that point to the old generation's files. Only 
> stopping / restarting the JVM frees the disk space for good.
> h3. Reproduction steps
>  * Connect to an existing TDB2 dataset
> {code}
> val dataset = TDB2Factory.connectDataset("sample"){code}
>  * Check open files
>   [^open_files_before_compaction.png]
>  * Compact the dataset
>   {code}DatabaseMgr.compact(dataset.asDatasetGraph){code}
>  * Check open files (before garbage collection)
>  [^open_files_after_compaction_before_gc.png]
>  * Check open files (after garbage collection)
>  [^open_files_after_compaction_after_gc.png]
> The last sceenshot shows that, even after garbage collection, there are still 
> open file descriptors pointing to the old generation {{Data-0001}}.
> h3. Impact
> Depending on how disk usage is being reported, this can be quite problematic. 
> In our case, we're running on an OpenShift infrastructure with limited 
> storage. After only a handful of compactions, the storage is considered full 
> and cannot be used anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)