Changing Cache Configuration at runtime in Infinispan
by Faseela K
Hi,
Does Infinispan support dynamically changing the cache configuration?
For example, I need a cache to run in transactional configuration for sometime,
and then I want to switch it to non-transactional configuration.
Thanks,
Faseela
12 years, 10 months
Infinispan 6.0.0.Beta1 is out!
by Mircea Markus
Dear Infinispan community,
We are proud to announce the first Beta release of Infinispan 6.0.0. This is an important milestone in the 6.0.0 lifecycle: it is feature and API complete.
Included in this release, you can find:
• a complete implementation of the remote-query functionality, including index management through JMX . Adrian Nistor will blog on this in the following days
• allow configuring the number of segments per node allows one to configure an uneven load of data between the nodes int the cluster. Dan Berindei will add a blog on this shortly
Together with this release we're also launching our new website:
• Built with Awestruct. Yes, it really is awesome and fun to use
• Hosted on GitHub Pages. Quick and easy.
• Styled with JBoss.org Community's flavour of Twitter Bootstrap
• Documentation reformatted/moved from Confluence to AsciiDoc
Among other things, the new site reflects some changes in the way Infinispan is distributed - including several cache stores and Hot Rod clients being moved out to separate GitHub repositories and following their own release cycles.
We think it's pretty slick and pretty sure you wouldn't guess its written by a hardcore backed developer! Kudos to Manik Surtani for such a nice job!
Last but certainly not least, a BIG thanks to our colleagues from the Hibernate team for their support (that is enhancements, fixes and releases and unreasonable hours) in getting the remote query functionality in time!
For a complete list of features and fixes included in this release please refer to the release notes.
Visit our downloads section to find the latest release and if you have any questions please check our forums, our mailing lists or ping us directly on IRC.
Thanks to everyone for their involvement and contribution!
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
12 years, 10 months
stack trace in my logs
by Kurt T Stam
Hi guys,
I'm running on OSX with ModeShape 3.2.0.Final which depends on ISPN
version 5.1.6.FINAL
and sometime I see this stack in my log. Everything seems to be working
ok anyway though.
http://pastebin.test.redhat.com/163600
Is this something you guys have seen before?
Thx,
--Kurt
12 years, 10 months
JGRP-1317 and large clusters
by Bela Ban
FYI,
if you're running large clusters, you might be interested to know that I
implemented another optimization: JGRP-1317 [1].
The effect of it is that (in decreasing order of importance):
- Regular view messages to existing members don't carry a digest any
longer. This is a significant size reduction, as a digest has 2 longs
per member (although compressed for network transmission)
- Where we have a view and a digest (e.g. JoinRsp, merge response,
MergeView), the digest's 'members' field and the view's 'members' field
point to the same memory location
- When we send such an object across the network, the 'members' field is
only marshalled once, leading to smaller messages
Next up, I'm going to tackle [2] which will reduce the size of view
messages even further: instead of sending the *full view* every time, we
only send delta views. I believe JGRP-1317 and JGRP-1354 will have a
huge impact on systems with a large number of nodes.
[1] https://issues.jboss.org/browse/JGRP-1317
[2] https://issues.jboss.org/browse/JGRP-1354
--
Bela Ban, JGroups lead (http://www.jgroups.org)
12 years, 10 months
JGroups 3.4.0.Beta1
by Bela Ban
FYI,
I released 3.4.0.Beta1 yesterday. It contains delta views [1] and
compressed merge views [2]. Useful in large clusters, delta views
dramatically reduce the message size needed to install a new view, by
sending only the diff to the previous view. E.g. if we have
v5={A,B,C,D,E} and F joins, A will only send v6={v5 +F}, and everybody
will construct a new view v6={A,B,C,D,E,F}.
The message size of a new view is therefore only a function of the
number of members which joined or left, and not a function of the entire
cluster size.
Full views are only sent when the first view of a coordinator is sent,
e.g. if A crashes and B takes over, B would send the full view.
Delta views can be turned off by seting GMS.use_delta_views=false.
3.4.0.Beta1 can be downloaded from SourceForge [3] or Nexus [4].
3.4.0.Beta1 should be the last (and only) beta, I intend to release
3.4.0.Final in early October.
Cheers,
[1] https://issues.jboss.org/browse/JGRP-1354
[2] https://issues.jboss.org/browse/JGRP-1391
[3] https://sourceforge.net/projects/javagroups/files/JGroups/3.4.0.Beta1
[4]
http://search.maven.org/remotecontent?filepath=org/jgroups/jgroups/3.4.0....
--
Bela Ban, JGroups lead (http://www.jgroups.org)
12 years, 10 months
