The issue here is that HiveServer2 contains state. This is true for any query regardless of Knox. Any JDBC client connecting to HS2 needs to disconnect and reconnect on failure. There are no workarounds for this. With HS2 and Zookeeper, the client must disconnect on failure and reconnect at which point the client will ask ZK for a new server. Knox works the same way in that if there is a failure, the client must disconnect and reconnect. If the client doesn't disconnect/reconnect then there is a chance to get weird errors. Work is not preserved moving between HS2 instances in many cases.
Kevin Risden On Tue, Oct 16, 2018 at 4:29 AM rabii lamriq <[email protected]> wrote: > Hi Larry > > Thank you for your quick reply, my goal is to create two 4 instances (2 > http and 2 binary) and configure HA + load balancing. > I tested HA of Hiveserver2 through zookeeper, it's work well, but the ZK > doesn't support automatic failover. However, Knox support HA with failover > but without load balancing. > > Is there any solution of configuration to make hybrid solution using both > Knox and ZK, > > also, how to test failover via Knox, I am using DBvisualizer as client to > connect to Hive using Knox. > > Regards > Rabii > > Le lun. 15 oct. 2018 à 14:51, larry mccay <[email protected]> a écrit : > >> Hi Rabii - >> >> Proxying HS2 through Knox requires HTTP mode. >> Binary is not supported at all. >> >> thanks, >> >> --larry >> >> On Mon, Oct 15, 2018 at 3:15 AM rabii lamriq <[email protected]> wrote: >> >>> Hi >>> >>> Is binary mode of Hiveserver2 supported by knox? If yes, how to >>> configure HA between 4 HS2 instances (2 in http and 2 in binary mode) >>> >>> Best >>> Rabii >>> >>
