[
https://issues.apache.org/jira/browse/IGNITE-14491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Safonov updated IGNITE-14491:
------------------------------------
Description:
{color:#000000}ThinClientKubernetesAddressFinder is mentioned here:{color}
[[https://ignite.apache.org/docs/latest/thin-clients/java-thin-client#partition-awareness]
- Please describe when to use it.
- See the relevant issue below:
_Check this section of the AWS EKS page:
[https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment#partition-awareness]_
__
_The Partition Awareness is a top-level section and the "Connecting to REST
API" is placed under it. Which is wrong. The Partition Awareness must be
located as a sub-section of the "Connecting with Thin Clients" section that is
above. If it's impossible to have another level under this tree then rename:_
- Remove this statement form the Partition Awareness everywhere. Double check
with Pavel Tupytsin.
_"Note that for non-Java clients presently you need to provide addresses of
all the server nodes in the connection properties. This also means that if a
new server node joins the cluster, you should add the server’s address to the
connection properties and reconnect the thin client. Otherwise, the thin client
will not be able to send direct requests to this server. This limitation is
planned to be addressed before the GA release of the feature."_
* _"Partition Awareness" -> "Connecting with Thin Clients and Partition
Awareness"_
- This needs to be done for Azure and Google Pages as well.
Consult with dev team for more details.
was:
{color:#000000}ThinClientKubernetesAddressFinder is mentioned here:{color}
[https://ignite.apache.org/docs/latest/thin-clients/java-thin-client#partition-awareness
- Please describe when to use it.
- See the relevant issue below:
_Check this section of the AWS EKS page:
[https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment#partition-awareness]_
__
_The Partition Awareness is a top-level section and the "Connecting to REST
API" is placed under it. Which is wrong. The Partition Awareness must be
located as a sub-section of the "Connecting with Thin Clients" section that is
above. If it's impossible to have another level under this tree then rename:_
- Remove this statement form the Partition Awareness everywhere. Double check
with Pavel Tupytsin.
_"Note that for non-Java clients presently you need to provide addresses of all
the server nodes in the connection properties. This also means that if a new
server node joins the cluster, you should add the server’s address to the
connection properties and reconnect the thin client. Otherwise, the thin client
will not be able to send direct requests to this server. This limitation is
planned to be addressed before the GA release of the feature."_
* _"Partition Awareness" -> "Connecting with Thin Clients and Partition
Awareness"_
- This needs to be done for Azure and Google Pages as well.
Consult with dev team for more details.
> Docs on ThinClientKubernetesAddressFinder
> -----------------------------------------
>
> Key: IGNITE-14491
> URL: https://issues.apache.org/jira/browse/IGNITE-14491
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Nikita Safonov
> Priority: Major
>
> {color:#000000}ThinClientKubernetesAddressFinder is mentioned here:{color}
>
> [[https://ignite.apache.org/docs/latest/thin-clients/java-thin-client#partition-awareness]
> - Please describe when to use it.
> - See the relevant issue below:
> _Check this section of the AWS EKS page:
> [https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment#partition-awareness]_
> __
> _The Partition Awareness is a top-level section and the "Connecting to REST
> API" is placed under it. Which is wrong. The Partition Awareness must be
> located as a sub-section of the "Connecting with Thin Clients" section that
> is above. If it's impossible to have another level under this tree then
> rename:_
> - Remove this statement form the Partition Awareness everywhere. Double
> check with Pavel Tupytsin.
>
> _"Note that for non-Java clients presently you need to provide addresses of
> all the server nodes in the connection properties. This also means that if a
> new server node joins the cluster, you should add the server’s address to the
> connection properties and reconnect the thin client. Otherwise, the thin
> client will not be able to send direct requests to this server. This
> limitation is planned to be addressed before the GA release of the feature."_
>
> * _"Partition Awareness" -> "Connecting with Thin Clients and Partition
> Awareness"_
> - This needs to be done for Azure and Google Pages as well.
> Consult with dev team for more details.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
