Thursday, 28 May 2020
One of the key aspects of our new server architecture is the management API exposed through the single port.
While I’m sure there will be those of you who like to write scripts with plenty of
curl/wget magic, and those who prefer the comfort of our new web console, the Infinispan CLI offers a powerful tool which combines the power of the former with the usability of the latter.
During the Infinispan 11 development cycle, the CLI has received numerous enhancements. Let’s look at some of them !
When using the built-in properties-based security realm, you had to use the
user-tool script to manage users, passwords and groups. That functionality has now been built into the CLI:
[disconnected]> user create --password=secret --groups=admin john [disconnected]> connect --username=joe --password=secret [infinispan-29934@cluster//containers/default]>
You can now modify the server logging configuration from the CLI. For example, to enable TRACE logging for the
org.jgroups category, use the following:
[infinispan-29934@cluster//containers/default]> logging set --level=TRACE org.jgroups
|logging configuration changes are volatile, i.e. they will be lost when restarting a node.|
To help with debugging issues, the server now implements an aggregate log which includes information such as a thread dump, memory configuration, open sockets/files, etc.
[bespin-29934@cluster//containers/default]> server report Downloaded report 'infinispan-bespin-29934-20200522114559-report.tar.gz'
|this feature currently only works on Linux/Unix systems.|
It is now possible to invoke all CLI commands directly from the command-line, without having to resort to interactive mode or a batch. For example:
cli.sh user create --password=secret --groups=admin john
The CLI can now be built as a native executable, courtesy of GraalVM's
native-image tool. We will soon be shipping binaries/images of this, so look out for an announcement.
Tags: cli server management administration logging
Thursday, 28 April 2011
The first candidate release of the Infinispan 5.0 "Pagoa" series is out now. The final features added include:
Lock identifiers are now available to Infinispan users in order to help reorder lock acquisitions which helps reduce the possibility of deadlocks.
Infinispan now supports internationalization of messages as per the rules here. The internationalization of messages is not yet available, but the integration of JBoss Logging into Infinispan would allow it in an easy way.
In the last BETA we renamed the lazyDeserialization XML element to storeAsBinary but this resulted in previous XML configurations not been valid any more. So, we’ve reinstated the lazyDeserialization element but if you use it, you’ll see a WARN message indicating that you should replace it with storeAsBinary.
A very important change in the release is the change of the default value for lock striping configuration. In previous releases, this used to be enabled by default but as hinted in its documentation this can cause deadlocks. So, after some debate, we’ve decided to disable it by default.
New EC2 demo available in the all zip distribution with examples of distributed executors and map/reduce! Make sure you try it out :)
There’s some other minor fixes as shown in the release notes. As always, please use the user forums to report back, grab the release here, enjoy and keep the feedback coming. The Final version is not far away, so make sure you test this CR! :)
Tags: internationalization logging lock striping