In Varnish there are some differences between VCL 2.x and 3.0. Hash generation for example. In Varnish 2.x you'd do req.hash += somevar while in Varnish 3.x you would call hash_data(somevar).
Is it possible to write portable Varnish scripts that work on both 2.x and 3.x? Can I if on the Varnish version for example?
No, it's not possible since Varnish compile vcl configs in C prior to start, so you should translate the config to the right version before or you will get a compile error.
Related
I'm looking for the older cookie vmod (libvmod_cookie.so) to use with varnish-cache v.5.0. I know that's pretty old but I'm locked in for now. Everything now points to git, which doesn't have it because it's been part of varnish since 6.4. Where to find it?
The source code for vmod_cookie can be found on https://github.com/varnish/varnish-modules.
Unfortunately Varnish Cache 5.x is end-of-life, but if you really want to dig up a version, you can browse through the commits.
While vmod_cookie has been an in-tree VMOD for Varnish Cache for a number of releases now, https://github.com/varnish/varnish-modules/tree/6.0/src still has it. Maybe check https://github.com/varnish/varnish-modules/blame/6.0/src/vmod_cookie.c and see how much it differs.
It may be a bit of work, but you might be able to compile that code, or at least a historic version of that code on 5.x.
No guarantees though, because remember: 5.x is end-of-life.
My advice: run Varnish Cache 6.0 LTS. See https://www.varnish-software.com/developers/downloads/#linux-packages
Current Jmeter version -5.2.1
I even tried by setting up the classpath as below in the jmeter.properties file -
user.classpath=/usr/local/Cellar/groovy/3.0.4/libexec/lib
Kindly help
Current JMeter version is 5.3 and according to 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article you should be always using the latest stable JMeter version, it can be obtained from JMeter Downloads page
JMeter 5.2.1 comes with Groovy 2.4.16, it might be better to stick to that version just in case
You need to restart JMeter in order to pick up any properties or classpath changes
If you installed JMeter using Homebrew it might be the case the Groovy library was deleted by someone by accident, you can get it back like brew reinstall jmeter.
And last by not the least you can always drop the library(ies) you need to add to JMeter to /usr/local/Cellar/jmeter/5.2.1/libexec/lib/ folder
I need to dump data from Nutch 2.3 into a WARC file. However, i couldn't find the necessary module. Nutch 1.x had this capability. I would like to know the proper way to do it.
As you said, at the moment the WARC exporter module is not yet ported to the 2.x branch of Nutch, nevertheless porting the https://github.com/apache/nutch/blob/master/src/java/org/apache/nutch/tools/warc/WARCExporter.java module shoudln't be that hard. As a general rule the 1.x branch of Nutch still is more used and better equiped than the 2.x branch (at least for now).
I have infinispan 6.0, want to upgrade it to 7.2.5, and keep the config files same, but upgrade the binaries.
Parsers for 6.x-style configuration have been dropped. If you insist on using old configuration files, you have to write your own parser (or rather port the parser from 6.0 to changes in programmatic API).
Another option is to use commmercial JDG 6.6 which includes most of the features from 7.2.5 but still uses the old configuration format for compatibility.
Updating your config is the easiest way.
I'm trying to profile a web application with xDebug and Webgrind since I'm doing it in a remote Linux server. For some weird reason it doesn't show call names or file source. I was suspecting that there might be some kind problem with readying the script files (not sure if it's doing it) but giving target folders 777 didn't make any difference. Does anybody have a clue where I'm failing?
Thanx!
The webgrind version found on google code does not work for xDebug 2.3.
Here is a fork that works: webgrind
Ok, 24h later:
Seems that webcache grind doesn't support cachegrind file function compression feature that was introduced in xDebug 2.3 (released 2015). The latest webgrind was released ~2008-2009 so makes sens that it doesn't work. The same applies to WinCacheGrind client. Currently seems that only Windows cachegrind analyzer is qCacheGrind and linux client kCacheGrind
When I maange to find some free time I'll fork the project and make it compatible with compression.