timoninmaxim commented on a change in pull request #8532:
URL: https://github.com/apache/ignite/pull/8532#discussion_r561860393



##########
File path: docs/_docs/installation/kubernetes/generic-configuration.adoc
##########
@@ -388,6 +388,20 @@ Note that we use the external IP address (LoadBalancer 
Ingress) of the service.
 include::{javaFile}[tags=connectThinClient, indent=0]
 ----
 
+== Partition Awareness
+
+include::../../includes/partition-awareness.adoc[]
+
+To enable the partition awareness feature within scaling Kubernetes enviroment 
one should start a client within the cluster and configure it with 
`KubernetesConnectionConfiguration`.
+In this case, a client can connect to every pod in a cluster.
+
+Note that client configuration must be in sync with Ignite node configuration.

Review comment:
       Agree, looks confusting. Remove this sentence at all.

##########
File path: docs/_docs/thin-clients/java-thin-client.adoc
##########
@@ -86,6 +86,16 @@ The following code sample illustrates how to use the 
partition awareness feature
 include::{sourceCodeFile}[tag=partition-awareness,indent=0]
 ----
 
+If list of server nodes is dynamically changing or scaling than it is possible 
to configure connection with custom implementation of `ClientAddressFinder`. It 
should provide actual server addresses collection for every time client ask it.
+The following code sample illustrates how to use it.
+
+[source, java]
+----
+include::{sourceCodeFile}[tag=client-address-finder,indent=0]
+----
+
+Currently Ignite provides the only implementation of this interface. 
`ThinClientKubernetesAddressFinder` is created to handle scalable Kubernetes 
environment.

Review comment:
       @Nikita-tech-writer I've updated the docs. Could you please check it?




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to