Hello, DataStax Community!

We want to make you aware of a few operational updates which will be carried out on the site. We are working hard to streamline the login process to integrate with other DataStax resources. As such, you will soon be prompted to update your password. Please note that your username will remain the same.

As we work to improve your user experience, please be aware that login to the DataStax Community will be unavailable for a few hours on:

  • Wednesday, July 15 16:00 PDT | 19:00 EDT | 20:00 BRT
  • Thursday, July 16 00:00 BST | 01:00 CEST | 04:30 IST | 07:00 CST | 09:00 AEST

For more info, check out the FAQ page. Thank you for being a valued member of our community.


scano_183208 avatar image
scano_183208 asked ·

How do you configure alwaysonSQL?

I have been having trouble accessing Spark SQL via the studio UI interface. I have always on sql running in all of the nodes yet I am still unable to connect via studio. When checking the status on the nodes it says alwayson sql is running on a private IP.

How do I change the IP always on-sql is running on?

10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered ·

@scano_183208 The AlwaysOn SQL Service (AOSS) binds to the native transport address in cassandra.yaml so if AOSS is running on the private IP, it indicates that the native transport is unset and defaults to the same IP as the listen_address.

Set native_transport_address to the public IP on each node in cassandra.yaml to make it accessible to clients. For more information, see Using AlwaysOn SQL service. Cheers!

8 comments Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

@Erick Ramirez

Thank you Erick! I changed all of the nodes native transport address to the public IP while the listen address is the private IP and I am still unable to connect to the AOSS service via studio.

I am also running DSE studio on my local computer while the DSE node is located in a vm with its own addresses.

Any other ideas?

thanks in advance!

0 Likes 0 · ·

@scano_183208 it sounds like you have a NATing issue. If you can't telnet to the AOSS port (default 10000) from your PC/laptop then it's not a software issue and you need to resolve the network connectivity problem. Cheers!

0 Likes 0 · ·

@Erick Ramirez

thanks Erick! Quick question, when using telnet, do I telnet using my local computers command prompt? Also do I Telnet to the nodes publicIP:10000? Or just :10000?

thank you!

0 Likes 0 · ·

@scano_183208 if AOSS is bound to the public IP then yes, you telnet to it. Cheers!

0 Likes 0 · ·

@Erick Ramirez

Hi Erick,

Sorry for all the back and forth but when AOSS is bound to the public IP that means that the native transport address is the public, correct?

0 Likes 0 · ·

Also currently my Cassandra.yaml file has the native transport address set to public and the listen and native transport broadcast address set to private. Then I do a AOSS status and it return that the service is running on the private IP port 10000. Is this what I should see? When I attempt to make the listen address public it does not allow me. Throws a binding error.

0 Likes 0 · ·

Don't set native_transport_broadcast_address to a private IP or AOSS will be bound to the private IP.

ONLY set the following in cassandra.yaml:

  • listen_address: public_ip
  • native_transport_address: private_ip

You can check what IP port 10000 is bound to with the following command:

$ sudo lsof -nPi | grep LISTEN | grep java

Good luck! Cheers!

0 Likes 0 · ·

@Erick Ramirez Thank you so much! After making the native_transport_address the public IP and making some changes to the network, Spark SQL finally worked via DSE Studio.

Happy new years! Thanks again!

0 Likes 0 · ·