[
https://issues.apache.org/jira/browse/DERBY-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571480#action_12571480
]
Serge Tsv commented on DERBY-3437:
----------------------------------
Hello!
I'm trying to figure out if there's more then one instance of a particular
replication-related thread could be started by a Derby engine.
If this is the case, then by defining some hardcoded name for each thread could
possibly result in more then one thread running with a same name (it's possible
to have more then one thread with a same name). I depends on how it's important
from a debugging perspective then. But a name per thread type scheme will be
much easier to implement and support I suppose.
By the way, I haven't found any public user-docs related to a replication in
Derby. I guess it's still under development then and is not included into a
recent public stable builds. Could there be any requirements/development
documents which might give more information about Derby replication (besides
the source code and java docs)?
Thanks!
> Give all replication threads meaningfull names
> ----------------------------------------------
>
> Key: DERBY-3437
> URL: https://issues.apache.org/jira/browse/DERBY-3437
> Project: Derby
> Issue Type: Improvement
> Components: Newcomer, Replication
> Affects Versions: 10.4.0.0
> Reporter: Jørgen Løland
> Assignee: Serge Tsv
> Priority: Minor
>
> Some threads are created for replication purposes:
> * The log shipper thread on the master
> (o.a.d.i.services.master.MasterController)
> * The database boot thread on the slave (o.a.d.i.db.SlaveDatabase)
> * The log receiver thread on the slave
> (o.a.d.i.services.slave.SlaveController)
> These threads should be given names to simplify debugging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
