Mahesh, Do you have logs from the following thick client? TcpDiscoveryNode [id=5204d16d-e6fc-4cc3-a1d9-17edf59f961e, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 192.168.1.171], sockAddrs=[/0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, /192.168.1.171:0], discPort=0, order=1146, intOrder=579, lastExchangeTime=1569947734191, loc=false, ver=2.7.6#20190911-sha1:21f7ca41, *isClient=true*] I need to check it, may be I'm missing something.
пт, 4 окт. 2019 г. в 05:08, Mahesh Renduchintala < mahesh.renduchint...@aline-consulting.com>: > Hello Pavel, > > OK. I am a little bit not clear on the workaround you suggested on your > previous comment > >>>>As a workaround, I can suggest to not explicitly declare caches in the > client configuration. During joining to cluster process, the client node > will receive all configured caches from server nodes. > > In my scenario, > a) there are absolutely no caches declared on my thick client side. > b) The cache templates are declared on the server nodes and via SQL > generated from thick client side, the caches are created. > > How do I implement the workaround you suggested? > > regards > Mahesh > >
