Vladsz83 commented on code in PR #11003: URL: https://github.com/apache/ignite/pull/11003#discussion_r1374789803
########## docs/_docs/services/services.adoc: ########## @@ -234,6 +234,22 @@ tab:C++[] //== Accessing Services from Compute Tasks // TODO the @ServiceResource annotation +== Service Awareness [[service_awareness]] +For link:../thin-clients/java-thin-client.adoc#java_thin_client[Java Thin Client] you can activate Service Awareness. +To do that, enable link:../thin-clients/java-thin-client.adoc#partition_awareness[Partition Awareness]. + +When used, the thin client knows about nodes with the service instances and invokes them directly. + +Without Service Awareness, the invocation requests are sent to a random node. If it has no service +instance deployed, the request is redirected to a proper node. Such redirection costs. Review Comment: Fixed ########## docs/_docs/services/services.adoc: ########## @@ -234,6 +234,22 @@ tab:C++[] //== Accessing Services from Compute Tasks // TODO the @ServiceResource annotation +== Service Awareness [[service_awareness]] +For link:../thin-clients/java-thin-client.adoc#java_thin_client[Java Thin Client] you can activate Service Awareness. +To do that, enable link:../thin-clients/java-thin-client.adoc#partition_awareness[Partition Awareness]. + +When used, the thin client knows about nodes with the service instances and invokes them directly. + +Without Service Awareness, the invocation requests are sent to a random node. If it has no service +instance deployed, the request is redirected to a proper node. Such redirection costs. + +[NOTE] +==== +The service topology is updated asynchronously starting with the first service invocation. +Thus, few invocation redirects on the server nodes are still possible. Especially if the service migrates or was redeployed. Review Comment: Fixed -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
