incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-214) Allow to set Fuseki (or a single dataset) in read-only mode (and eventually, back into read-write mode)
Date Wed, 22 Feb 2012 20:41:48 GMT


Andy Seaborne commented on JENA-214:

This needs to "work nice" with the configuration file as that's the way everything should
be done.
To create a permanently read-only datasets, you configure in only read-only services.

Either this feature must know which services are write so as to set some flag as it's one
servlet instance per service per dataset or the config needs modifying carefully.

Maybe instantiate a wrapper service that has the old service, and is read-only, then when
the reverse is done, get only service and put back in place.

Or a wrapper for the dataset and change the dataset acted on.

The wrapper is only present while in a temporary read-only mode not permanently there although
that could be done as well.  Seems heavy weight for this special feature.
> Allow to set Fuseki (or a single dataset) in read-only mode (and eventually, back into
read-write mode)
> -------------------------------------------------------------------------------------------------------
>                 Key: JENA-214
>                 URL:
>             Project: Apache Jena
>          Issue Type: New Feature
>          Components: Fuseki
>            Reporter: Paolo Castagna
>            Priority: Minor
>         Attachments:
> 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
> 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:!default.jspa
For more information on JIRA, see:


View raw message