[
https://issues.apache.org/jira/browse/DERBY-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571728#action_12571728
]
Serge Tsv commented on DERBY-3437:
----------------------------------
I have attached a patch with defines names for log receiver thread and slave
boot thread.
I've decided to use a more conventional thread naming format, with a constant
part of the name on the left side of a minus sign, and a variable part - on the
right one.
As of now, a database name is not accessibly from a log shipper thread class.
To use a database name to name a log shipper thread would require one of the
following I guess
- pass the database name as a parameter to a log shipper constructor
- make dbname field package-protected in the MasterController class
- make a log shipper class an internal to MasterController (as a log
reciever class, which is defined as internal in SlaveController)
None of these solutions is perfect, but I haven't found any other ways that
could make db name available to log receiver...
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
> Attachments: DERBY-3437.diff
>
>
> 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.
