db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serge Tsv (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3437) Give all replication threads meaningfull names
Date Sat, 23 Feb 2008 12:31:19 GMT

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

Serge Tsv updated DERBY-3437:
-----------------------------

    Attachment: DERBY-3437.diff

Defines meaningful names for SlaveDatabaseBootThread thread instances created by SlaveDatabase,
and SlaveLogReceiverThread thread instances created by SlaveController.

The names have the format:
    
    derby.(slave or master).threadtype-dbname,

e.g derby.slave.boot-myDerby

> 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.


Mime
View raw message