Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Why more than one Knox service on the cluster?

avatar
Expert Contributor

Guys,

I see that on the cluster of 40 nodes, on three edge nodes, we have knox previously installed. I am not sure why some one would configure three edge nodes. What are the advantages of having more than one Knox instance when Knox does not run in HA.

1 ACCEPTED SOLUTION

avatar

@Smart Solutions

You can put several Knox instances behind a load balancer to have HA. So multiple Knox instances are required for HA

Knox documentation gives an example on how to do it with Apache HTTP Server https://knox.apache.org/books/knox-0-9-0/user-guide.html#High+Availability

View solution in original post

2 REPLIES 2

avatar

Hi @Smart Solutions

The main reason I see is to distribute load in case you have a lot of clients connecting to the edge nodes. You could imagine a load balancer in front of your Knox instances to distribute the load with only one entry point for your clients.

avatar

@Smart Solutions

You can put several Knox instances behind a load balancer to have HA. So multiple Knox instances are required for HA

Knox documentation gives an example on how to do it with Apache HTTP Server https://knox.apache.org/books/knox-0-9-0/user-guide.html#High+Availability