[
https://issues.apache.org/jira/browse/IGNITE-15417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408697#comment-17408697
]
Alexander Lapin commented on IGNITE-15417:
------------------------------------------
[~maliev] In general LGTM, one minor only: let's use
org.apache.ignite.lang.IgniteUuidGenerator#randomUuid for IgniteUuid generation
instead of new IgniteUuid(UUID.randomUUID(), 0L).
> Create cursorId on client side
> ------------------------------
>
> Key: IGNITE-15417
> URL: https://issues.apache.org/jira/browse/IGNITE-15417
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Original Estimate: 72h
> Time Spent: 20m
> Remaining Estimate: 71h 40m
>
> There is a bug in {{MetaStorageListener}} for {{RangeCommand}},
> {{WatchRangeKeysCommand}}, {{WatchExactKeysCommand}} commands in case cluster
> has several raft nodes, currently we create new {{cursorId}} for this
> commands on server side on a single client request, which means that one
> logical cursor is created for every {{MetaStorageListener}} on server side.
> This bug leads to a critical problem for cluster with several nodes because
> cursors won't be replicated correctly.
> We should create {{cursorId}} only on client side en pass it to server.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
