The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Justin R. Andrusk" <jra@andrusk.com>
To: Arthur Krewat <krewat@kilonet.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Steve Bellovin recounts the history of USENET
Date: Sat, 23 Nov 2019 01:32:16 +0000	[thread overview]
Message-ID: <20191123013213.GA30784@hal9k> (raw)
In-Reply-To: <d8dc0b57-6777-1b30-75a9-ab720a8e2f5c@kilonet.net>

On Fri, Nov 22, 2019 at 06:21:49PM -0500, Arthur Krewat wrote:
> 
> On 11/22/2019 3:18 PM, Justin R. Andrusk wrote:
> > I'm half tempted to take the archive.org Usenet files and throw them
> > into Elasticsearch and create a web front end for searching. Storage
> > would be expensive, but search would rock!
> 
> Can we run multiple nodes of Elastic, and replicate between each other?
> 
> I just recently started playing with it, it's quite impressive. Except
> for that one logstash file "read" mode that by default deletes the file
> once it's done with it (a 4-year-long access.log that I wanted to read in).
> 
> anyway.
> 
> art k.

Yes, that's how the clustering works with Elasticsearch. You setup
multiple nodes that are part of a cluster and data is replicated across
all of them. If one goes down, you don't lose any data as the others
will reconstitute the data. 

Going to look at adding the Usenet data to a Graylog instance as that
uses Elasticsearch as a backend and the front end UI is already there to
give you a GUI for searching and doing analytics on what you send to it.

Justin


  reply	other threads:[~2019-11-23  1:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 12:46 Jason Stevens
2019-11-21 13:23 ` arnold
2019-11-21 13:31   ` Jason Stevens
2019-11-21 15:58   ` Leah Neukirchen
2019-11-22 20:18     ` Justin R. Andrusk
2019-11-22 20:49       ` Henry Bent
2019-11-22 21:06         ` Kurt H Maier
2019-11-22 21:32           ` Larry McVoy
2019-11-23  1:48             ` Jason Stevens
2019-11-23  3:45               ` Larry McVoy
2019-11-23  4:42                 ` Warren Toomey
2019-11-22 22:21           ` Henry Bent
2019-11-23  0:00             ` Kurt H Maier
2019-11-23  1:36               ` Theodore Y. Ts'o
2019-11-22 23:21       ` Arthur Krewat
2019-11-23  1:32         ` Justin R. Andrusk [this message]
2019-11-23 22:25           ` Arthur Krewat
2019-11-21 17:22 ` Tomasz Rola
  -- strict thread matches above, loose matches on Subject: below --
2019-11-19 19:01 Arnold Robbins
2019-11-21  3:14 ` Larry McVoy
2019-11-21  3:18   ` George Michaelson
2019-11-21  3:28     ` Larry McVoy
2019-11-21  8:56       ` George Michaelson
2019-11-21  9:40         ` Bakul Shah
2019-11-21  9:51           ` George Michaelson
2019-11-21 11:16         ` Arrigo Triulzi
2019-11-21  3:34   ` reed
2019-11-21  3:39     ` Larry McVoy
2019-11-21  3:40   ` Chet Ramey
2019-11-21  3:42     ` Larry McVoy
2019-11-21  3:50       ` Chet Ramey
2019-11-21  3:51         ` Larry McVoy
2019-11-21  3:58           ` Steve Nickolas
2019-11-21  3:50   ` Bakul Shah
2019-11-21  3:52     ` Larry McVoy
2019-11-21  3:58       ` Bakul Shah
2019-11-21 20:36   ` Dave Horsfall
2019-11-24  2:19   ` Michael Parson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191123013213.GA30784@hal9k \
    --to=jra@andrusk.com \
    --cc=krewat@kilonet.net \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).