Reg:Cluster is not operational

Hello Experts,

Recently we have done the migration wM9.0 to wM9.10.

Everything came fine but we have done 2 node cluster by using TC.

But I’m able to see following 1000s of error messages in IS server log.
The cluster is now not operational.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 1749b6b0751617dbbd28ffffffffd821 to the session cache. put timed out.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 1749b6b0751617dbbd28ffffffffd821 to the session cache. put timed out.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.
2017-07-12 09:52:55 EDT [ISS.0033.0154E] Could not save session 1749b6b0751617dbbd28ffffffffd821 to the session cache. put timed out.
2017-07-12 09:52:55 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.
2017-07-12 09:52:55 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.

Because of this of this reason IS going down periodically.but we really need to determine what is killing our system.

Can you please suggest on this issue.

Thanks in advance.

Thanks,
Ram.

Can you check the below points:

1> Restart the IS cluster nodes
2> Make sure you have the latest fix installed for your version
3> Check if there are any network issues during these errors
4> Need the memory size assigned to TSA and IS?
5> Export the diagnostic file from IS when you encounter the issue (analyze the server logs for more details)

@Mahesh

we Installed IS in Two nodes one node is periodically going off.another node working fine.

Exported the diagnostic logs from IS Nonthing I found in logs.

I haven’t seen any network issues till now.

How to increase the TSA memory size without using TMC console?

Thanks,
Ram.