ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7339) RENTING partition is not evicted after restore from storage
Date Wed, 06 Jun 2018 08:56:00 GMT

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

Alexei Scherbakov commented on IGNITE-7339:
-------------------------------------------

[~dpavlov],

Patch available = pull request is ready, no ?

I see the following by the link [1]:

Submitting for Review
Attach a patch, pull request url or branch name (see instructions at Workflow)
(OPTIONAL) create an Upsource review: Review With Upsource
Add comment describing what has been implemented.
Move ticket to PATCH AVAILABLE state.

TC completion is never mentioned.

BTW, TC run looks acceptable, please review.

[1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview

> RENTING partition is not evicted after restore from storage
> -----------------------------------------------------------
>
>                 Key: IGNITE-7339
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7339
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Semen Boikov
>            Assignee: Alexei Scherbakov
>            Priority: Critical
>
> If partition was in RENTING state at the moment when node is stopped, then after restart
it is not evicted.
> It seems it is an issue in GridDhtLocalPartition.rent, 'tryEvictAsync' is not called
is partition was already in RENTING state.
> Also there is error in GridDhtPartitionTopologyImpl.checkEvictions: partition state is
always treated as changed after part.rent call even if part.rent does not actually change
state.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message