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

Paolo Castagna updated JENA-214:
--------------------------------

    Attachment: ActionReadOnly.java

This is my incomplete attempts at implementing this. 

I failed to do it since I don't see:
 - how to make a SPARQLServer going read-only and/or a single dataset
 - how to wait for all the write transactions to finish
 - how to ensure the journal as been applied to the database?

I am sharing this anyway, just in case others are interested in the same 
feature and have useful suggestions/ideas.
                
> Allow to set Fuseki (or a single dataset) in read-only mode (and eventually, 
> back into read-write mode)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JENA-214
>                 URL: https://issues.apache.org/jira/browse/JENA-214
>             Project: Apache Jena
>          Issue Type: New Feature
>          Components: Fuseki
>            Reporter: Paolo Castagna
>            Priority: Minor
>         Attachments: ActionReadOnly.java
>
>
> A very useful MgtCmdServlet with commands such as: "backup", "shutdown", etc. 
> is now available in Fuseki.
> This is proposing a new command to set the server (or a single dataset) in 
> read-only mode and back into read-write mode.
> A use case for this would be to perform a replication via rsync, in order to 
> replicate TDB indexes from server A to server B both servers needs to be set 
> to read-only mode first, the replication can start, when it finishes both 
> servers can be configured back to read-write mode.
> Another use case would be, enabling a backup with an external tool or any 
> other operation which needs to have exclusive access to TDB indexes and/or 
> ensure all data has been flushed to disk and there are no in-flight write 
> transactions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to