[
https://issues.apache.org/jira/browse/IGNITE-26796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-26796:
-----------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Update javaDoc for ReplicaService#invoke
> ----------------------------------------
>
> Key: IGNITE-26796
> URL: https://issues.apache.org/jira/browse/IGNITE-26796
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Zlenko
> Assignee: Egor Kuts
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> JavaDoc for ReplicaService#invoke is not up to date with how actually method
> invocation works right now.
> There is at least section describing that we can receive an error in case if
> request was sent to an incorrect node.
> {code}
> * @see ReplicaUnavailableException If replica with given replication
> group id doesn't exist or not started yet.
> {code}
> From this description one could expect that such result could be returned as
> soon as request was sent. However we still will wait for transaction timeout
> to occur to return an error.
> It would be better to improve javaDoc here, so it will be easier to
> understand what behavior is expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
