tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poorna Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-190) Reduce Lock granularity for transaction operations
Date Mon, 05 Dec 2016 22:07:58 GMT

    [ https://issues.apache.org/jira/browse/TEPHRA-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723512#comment-15723512
] 

Poorna Chandra commented on TEPHRA-190:
---------------------------------------

There is also code in class {{TransactionManager}} like {{public int getInvalidSize()}}, etc.
that access non thread-safe objects without any locks. It would be good to fix such uses when
working on this JIRA.

> Reduce Lock granularity for transaction operations
> --------------------------------------------------
>
>                 Key: TEPHRA-190
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-190
>             Project: Tephra
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Poorna Chandra
>            Assignee: Poorna Chandra
>
> Transaction manager uses a common lock for all operations. This reduces the concurrency
of the operations since only one transaction can get a lock at any given time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message