Question on ElasticXL second member lightshot partition saturation during join progress in cluster

[Mattia140831]

Hello,

I am having an issue with an R82 ElasticXL cluster with VSNext enabled.
After installing the Jumbo Hotfix (Take 107), the process of adding the second member (im using two 6900 appliances) fails due to insufficient space in the lightshot partition.
In theory, shouldn't it automatically resize the lightshot partition to accommodate the size of the SMO image?

I have already seen the relevant SK for resolving this by manually setting the size; however, that article mentions automatic resizing, something that did not happen in my case.

the sk i used to solve the problem:
https://support.checkpoint.com/results/sk/sk184626

the point who triggered my question:

6. Wait for the automatic resize

• During the join process, the Lightshot partition is automatically resized:
  
  • From 14 GB to 23 GB
• Continue monitoring until this resize is completed.

Thanks for any replies. 

[emmap · Accepted solution]

It should automatically resize, but there's an issue in base R82 that means it sometimes doesn't work. It's resolved in R82.10.

[Mattia140831]

Will there be Jumbo Hotfixes for the base R82 release to fix the bug?

[emmap]

The issue is in the base image, JHFs are not added to the new cluster member until it is added to the cluster so putting the fix into the JHF won't resolve it. 

[Mattia140831]

Got it, thanks.