[
https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511386
]
Jørgen Løland commented on DERBY-2872:
--------------------------------------
>I'm going to be giving a lightning talk at OSCON on the state of Derby and I
>want to know what if anything I can say about this feature. It sounds as
>though some increment of functionality will be delivered in the 10.4
>timeframe. Will this functionality be complete enough that someone can use it?
>If so, can you characterize the kind of application that will benefit from the
>10.4 increment?
The intention is definitely to have working replication functionality in 10.4.
Exactly what will be implemented and how depends heavily on what the community
wants, so the guesses below may have to be changed. Also, if more people want
to contribute to this task, more functionality will make it into 10.4 :-)
I think it is very likely that in 10.4, replication will work. Some manual
steps will probably be required, e.g. to start the fail-over logic. The
replication functionality will be usable by all applications that want higher
availability than a single (point of failure) server can provide. However,
having to manually start fail-over may be unacceptable (take too much time) for
applications with the highest availability requirements. Furthermore, the
application should not contain super-secret data since security issues are
likely to not make it into this release. But again, the priorities may change
as community discussions progress.
> Add Replication functionality to Derby
> --------------------------------------
>
> Key: DERBY-2872
> URL: https://issues.apache.org/jira/browse/DERBY-2872
> Project: Derby
> Issue Type: New Feature
> Components: Miscellaneous
> Affects Versions: 10.4.0.0
> Reporter: Jørgen Løland
> Assignee: Jørgen Løland
> Attachments: proof_of_concept_master.diff,
> proof_of_concept_master.stat, proof_of_concept_slave.diff,
> proof_of_concept_slave.stat, replication_funcspec.html,
> replication_funcspec_v2.html, replication_funcspec_v3.html,
> replication_script.txt
>
>
> It would be nice to have replication functionality to Derby; many potential
> Derby users seem to want this. The attached functional specification lists
> some initial thoughts for how this feature may work.
> Dag Wanvik had a look at this functionality some months ago. He wrote a proof
> of concept patch that enables replication by copying (using file system copy)
> and redoing the existing Derby transaction log to the slave (unfortunately, I
> can not find the mail thread now).
> DERBY-2852 contains a patch that enables replication by sending dedicated
> logical log records to the slave through a network connection and redoing
> these.
> Replication has been requested and discussed previously in multiple threads,
> including these:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200504.mbox/[EMAIL
> PROTECTED]
> http://www.nabble.com/Does-Derby-support-Transaction-Logging---t2626667.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
