granule does not work in a multi app-server environment

[GoogleCodeExporter]

Granule was implemented in our environment, which has a lot of app servers.  
Users and their session data are migrated between servers for various reasons.  
When a user is migrated to a different app server the granule id in their 
browser cache is no longer invalid, because granule ids are based on a 
combination of a name hash and that server's system time.

Is it possible to have granule generate ids that are consistent across multiple 
app servers?  Would it be possible to remove the timestamp component of the 
generated ids?

Original issue reported on code.google.com by john_fel...@yahoo.com on 9 Aug 2011 at 11:28

[GoogleCodeExporter]

We faced the same issue.
http://thinkingofjava.blogspot.com/2011/10/grails-granule-plugin-cluster-problem
.html
If you want I can share more details how we forced it to work in our cluster 

Original comment by macs...@gmail.com on 22 Oct 2011 at 1:41

[GoogleCodeExporter]

Hi Macs,

I'd be very interested to know how you worked around this issue if you have 
time to tell.

Regards,

Kevin

Original comment by kevfl...@gmail.com on 4 Jan 2013 at 5:00

[GoogleCodeExporter]

I'd love to hear how anyone got this to work in a clustered environment too, 
please.

Original comment by Tony.Zer...@gmail.com on 21 May 2015 at 7:53