Solr Search Bundle 1.1 released

28 10 2011

The Solr Search v1.1 bundle developed for Nakamura has been released. This is not to be confused with Apache Solr 4. The bundle wraps a snapshot version of Apache Solr 4 at revision 1162474 and exposes a number of OSGi components that allow s SolrJ client to interact with the Solr server. This release adds a priority based queue to enable Quality of Service commitments to be made against a request to index a content item, and that item appearing in the index. Those commitments are fulfilled with parallel queues ensuring that the indexing happens within the requested time, not blocked by less urgent items. The queues are persistent and reliable ensuring that should a remote Solr server fail, the request to index will not be lost.  Optionally a deployer can specify that real time indexing is enabled using soft commits by configuration of the queue and the Solr server. Other improvements are listed with the issues fixed against this version, link below. Thanks goes to everyone who contributed and helped to get this release out.

 

Issues Fixed: https://github.com/ieb/solr/issues?sort=created&direction=desc&state=closed&page=1&milestone=2
Release Tag: https://github.com/ieb/solr/tree/org.sakaiproject.nakamura.solr-1.1

To Use from a maven2 project

 
    <dependency>
        <groupId>org.sakaiproject.nakamura</groupId>
        <artifactId>org.sakaiproject.nakamura.solr</artifactId>
        <version>1.2</version>
    </dependency>




Sparse Map Content 1.2 Released

27 10 2011

Sparse Map version 1.2 has been tagged (org.sakaiproject.nakamura.core-1.2) and released. Downloads of the source tree in Zip and TarGZ form are available from GitHub.

In this release 9 issues were addressed, the details are in the issue tracker. Notable contributions include a MondoDB driver from Erik Froese which missed the 1.1 release a month ago. After the last release it was suggested that the artfacts make it into a central place, and so all artifacts (binary, source and javadoc) have been signed and pushed up to the central repo. If you find any issues, please mention them to me or, better still, add an issue to the issue tracker. Unless otherwise stated the license is Apache 2. Thanks to everyone who made this release possible.

Tag:  https://github.com/ieb/sparsemapcontent/tree/org.sakaiproject.nakamura.core-1.2
Issues Fixed: https://github.com/ieb/sparsemapcontent/issues?sort=created&direction=desc&state=closed&page=1&milestone=3

To use

<dependency>
  <groupId>org.sakaiproject.nakamura</groupId>
  <artifactId>org.sakaiproject.nakamura.core</artifactId>
  <version>1.2</version>    
</dependency>

The Jar is an OSGi bundle complete with Manifest, bundled dependencies and services, ready for use in Apache Felix.





1990′s Internet

21 10 2011

Many years ago, when I migrated from dialup modem to cable the word broadband really did change your life. Always on, ping latencies below sub 500ms and ssh sessions that didnt resemble the teletype printer that used to broadcast the football results to the nation on Saturday at 5pm (for those that remember the 1970s). I was fortunate enough to be be in a rural UK village located between two nodes in what was then Cambridge Cables trunk network (later NTL, later Virgin). I was the first in this village to be connected, and I remember weeks of anticipation followed by dashed hopes as a stream of cable installation engineers visited. Eventually they admitted, that there was not enough signal getting to the door, and put in a slightly better quality cable. For almost 10 years after that, my Motorola Surfboard modem, connected to a UPS gave me broadband connectivity, 24x7x365 even through powercuts. Neve more than a few Mb/s but always on an always reliable sub 10ms latency with no packet loss.

Arriving in Sydney, in a 3G dark spot, I ordered up a Optus Cable connection and had a length of Coax strung from the nearest telegraph pole. It worked well at night and when the sun didnt shine. Over the past month thats been quite a lot. As soon as the sun shone the received power levels dropped below -10 dBmV and the the signal to noise ratio dropped below 35 dB. Packet loss started, DNS became horrible and the shiny 20Mb line became a 57K modem sitting in a microwave oven… if I was lucky. For fun, and to prove to Optus just how bad the connection was, I monitored the signal levels of the line with a script, the graphs are below. With power levels between -2 and +2 dBmV and signal to noise ratios about 40 dB if get solid connectivity. The rest of the time (power levels and SNR lower) all sorts of symptoms appear on the modem. In my case, on a day of about 27C with bright sun shine thats connectivity for about 1 minute every 5.

The Optus cable engineer arrived, looked at the graph, looked at the modem, looked at the telegraph pole, scratched his head and went up a ladder at the pole. 5 minutes later he came down with a 1997 Coax network tap. Corroded. Being at the end of the line, as in the UK village, I was the first to use the line (in years), and unfortunately GHz cant jump over a furred up connector.

For anyone with an awful net connection reading this post, and wondering if modem A or modem B will give them better performance, or if Optus is any better than Telstra, check you signal levels over time in sun and rain (refresh the page several times), you may have a corroded bit of the 1990s sitting between you and lighted fibre. If you do, the difference between 1Mb and 20Mb is probably irrelevant. Here are some keywords to help you find this post: Optus, Netgear CG3000, dropped, packets.








Follow

Get every new post delivered to your Inbox.

Join 122 other followers