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

Maksim Timonin edited comment on IGNITE-17272 at 7/25/22 9:33 AM:
------------------------------------------------------------------

[~apolovtcev]  [~ibessonov] 

Hi guys! This fix isn't fully correct. It leads to the InvalidMarkException 
while parsing encrypted records from WAL. 

I found that while investigating a reason of test ([1]) started failing. 
Actually there is a small fix [2], could you please have a look?

[1] https://issues.apache.org/jira/browse/IGNITE-17215

[2] https://issues.apache.org/jira/browse/IGNITE-17408


was (Author: timonin.maksim):
[~apolovtcev]  [~ibessonov] 

Hi guys! This fix isn't fully correct. It leads to the InvalidMarkException 
while parsing encrypted records from WAL. 

I found that while investigating a reason of test ([1]) started failing. 
Actually there is a small fix [2], could you please have a look? WDYT, should I 
add more tests here?

[1] https://issues.apache.org/jira/browse/IGNITE-17215

[2] https://issues.apache.org/jira/browse/IGNITE-17408

> Logical recovery works incorrectly for encrypted caches
> -------------------------------------------------------
>
>                 Key: IGNITE-17272
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17272
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.13
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>             Fix For: 2.14
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When encryption is enabled for a particular cache, its WAL records get 
> encrypted and wrapped in an {{EncryptedRecord}}. This encrypted record type 
> is considered a {{PHYSICAL}} record, which leads to such records being 
> omitted during logical recovery regardless of the fact that it can contain 
> logical records.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to