ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanilovsky Evgeny (Jira)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-13614) Potential bugs after [ignite-12701].
Date Fri, 23 Oct 2020 10:04:00 GMT
Stanilovsky Evgeny created IGNITE-13614:
-------------------------------------------

             Summary: Potential bugs after [ignite-12701].
                 Key: IGNITE-13614
                 URL: https://issues.apache.org/jira/browse/IGNITE-13614
             Project: Ignite
          Issue Type: Bug
          Components: general
    Affects Versions: 2.8.1
            Reporter: Stanilovsky Evgeny


 After [1] has been merged to master looks like there are a bit places without test coverage
where unexpected behavior could fired. 
1. GridClientClusterStateRequestV2 - new client send this class into old server = deserialization
problem.
2. GridClusterStateProcessor#hasInMemoryCache have no filter for sys-cache, thus "--force"
option will always be demanded.
[~vladsz83] [~nizhikov] take a look plz.

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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message