Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CA623200D57 for ; Mon, 11 Dec 2017 23:03:33 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C8D56160C13; Mon, 11 Dec 2017 22:03:33 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C08B4160C03 for ; Mon, 11 Dec 2017 23:03:32 +0100 (CET) Received: (qmail 80505 invoked by uid 500); 11 Dec 2017 22:03:31 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 80491 invoked by uid 99); 11 Dec 2017 22:03:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Dec 2017 22:03:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 4143FC65FE for ; Mon, 11 Dec 2017 22:03:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.899 X-Spam-Level: * X-Spam-Status: No, score=1.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qJmFX4XVDsjs for ; Mon, 11 Dec 2017 22:03:28 +0000 (UTC) Received: from mail-wr0-f174.google.com (mail-wr0-f174.google.com [209.85.128.174]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C904B63034 for ; Mon, 11 Dec 2017 17:57:36 +0000 (UTC) Received: by mail-wr0-f174.google.com with SMTP id a41so18513865wra.6 for ; Mon, 11 Dec 2017 09:57:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to; bh=9xUyFe3bvQnRanMGj6JUSmJKD+Esy7kj8VREqsExcpM=; b=ZEM+QQVZOREbxWJrXXZ6R1GDdPlsQ2y+dPV4TaHK9GrLpoX4QTuXAQY7d98iy0FIug PS+Vg7pFqGCwPPbBw6WDrGaz2yMu0piDnhfCf7yG6qH/qP2ZDaHWSk/Vz+HvIuqFj+GZ 5iNU1Mw2pu/TW6sIx0uItV0KoUzS+pO9RMDpGSa+i7cAek6Xrv7H7+Q6XzCVovo6l2od 2G1aXPzaXDD+cmzUow7NYD3aonlW6IgiMZizu67VOniF4W2ZJ1070Vqv5is88HzD9qpX 9d931I2awf5lF1LG+7CxSfu/yHQ09p7xlQFU5ogDPT0uBIs3yvM04Qo+R4GN88ZfBs7x BKYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=9xUyFe3bvQnRanMGj6JUSmJKD+Esy7kj8VREqsExcpM=; b=PNZr4NCDQ7JwRIOYRR68vvXkVhGv0diILdwb9L0JMslQSnf7p7v/MIrEEv0IdW3pVN brS9M+Rc77XpiFn4E/yXYh2lE38ghMBPDHhWzxY0zm6tidueAMItcnd/QPzge2acR5zd DiBdCJNucTE4FemhpdKtSaSyU6UsFn3d1Hup2q+AGqE0tm1VzkPkSe/X6KgqG8Jm0A3C O+/6nE7JIEvNFebNXuCDwzxsxrUH6teOgF2l0BG9mQ6M0EG92UVNsCVcn7Ow1JjoFZbK O3Bxj1QwkFXN5wPLb8OWyagRs72gdEQE8Ufj00eI2gm/lULigBL0Pmt9EFFeF59kQcTi l3IA== X-Gm-Message-State: AKGB3mLiX41ruX42XsnDeAePfRcF+B9VlYcxhlqLS4IOwRs0ch2T0R7/ bO2E+ceK/4jV5+OxvaF3a0Y2Okc9/A4qPbFf5A== X-Google-Smtp-Source: ACJfBoti2gTX3iiIs93tO/Uj3ebfw9BUdn4qPXyaBUrwRBPEe4VkOW59RPWqPwie15sFD0V8su2f5BFXwD0NGPnL0rw= X-Received: by 10.223.171.13 with SMTP id q13mr1196006wrc.120.1513015056296; Mon, 11 Dec 2017 09:57:36 -0800 (PST) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 11 Dec 2017 18:57:35 +0100 From: Steven van der Merwe In-Reply-To: <75D12191-9105-4C56-92C5-6D34DF314C4D@apache.org> References: <75D12191-9105-4C56-92C5-6D34DF314C4D@apache.org> X-Mailer: Airmail (467) MIME-Version: 1.0 Date: Mon, 11 Dec 2017 18:57:35 +0100 Message-ID: Subject: Re: Ignite use case To: Denis Magda , user@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c1b50baf86ea505601444d3" archived-at: Mon, 11 Dec 2017 22:03:34 -0000 --94eb2c1b50baf86ea505601444d3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Brilliant - Thanks for the pointers Dennis Regards Steve On 11 December 2017 at 19:43:37, Denis Magda (dmagda@apache.org) wrote: Hello Steve, Your use case perfectly well fits Ignite=E2=80=99s capabilities. Please see= inline for the rest. On Dec 11, 2017, at 6:00 AM, Steven van der Merwe < stevevandermerwe@gmail.com> wrote: Hi All I am new to Ignite and I am trying to understand if Ignite will fit my use case (I hope so). It seems to have all of the aspects I am looking for. I am trying to do the following: - I am building up a realtime analytics / business dashboard based on a whole lot of metrics and messages in the integration space (utilising something like a time series database). - I would like to stream messages from a number of different data collectors (I am using queues at the moment for this task) - - At the moment I am putting these messages into Graylog / Elasticsearch but I am looking to change this - I need to store the time series data in a DB (About 1-5 million messages a day) - - I want to evict / delete the data after a month or so (if space is a problem) - I need to do some basic aggregation and CEP - I would like to aggregate the data over time (and thus reduce the granularity / size) I guess my questions are the following: - Can I start using Ignite (in a single (or a few) nodes initially) as a SQL / KV store (I will probably persist the data to disk very soon only keeping a few 10-20GB in RAM and use it more like a traditional =E2=80= =9CDB=E2=80=9D)? Yes, the documentation section below explains how to define how much memory to dedicate in RAM and how to enable the persistence: https://apacheignite.readme.io/docs/memory-configuration#section-data-regio= ns - My concern is the Ignite was not designed for this (as it seems mostly in memory) so I am unsure about how it will work persisting 500-1000GB o= f data on a single node (I guess I am trying to use it more as a hybrid in memory store) Ignite 2.x is based on a completely new memory architecture where disk stores a subset of data and RAM caches as much data as you can afford. https://apacheignite.readme.io/docs/durable-memory So, presently Ignite is also used as a system of records or classical DB. - The documentation seems to refer to using it as a cache in front of a RDBMS but I would like to just use Ignite as the only DBMS What=E2=80=99s the documentation you=E2=80=99re referring to? There are man= y documentation and use cases pages Ignite is used for. For instance, the use cases on the site unveil how to use it as a DBMS: https://ignite.apache.org/usecases.html - Can I aggregate the data using time as a =E2=80=9Cgrouping" field ? - - I will delete the expired data from the db periodically - I want to do CEP on the data Yes Denis Thanks for the help in advance. Regards Steve --94eb2c1b50baf86ea505601444d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Brilliant - Thanks for t= he pointers Dennis

Regard= s
Steve




On 11 December 2017 at 19:43:37, Denis Magda (dmagda@apache.org) wrote:

Hello Steve,

Your use case perfectly well fits Ignite=E2=80=99s capabilities. Please see inline for the rest.

On Dec 11, 2017, at 6:00 AM, Steven van der Merwe <stevevandermer= we@gmail.com> wrote:

Hi All

I am new to Ignite and = I am trying to understand if Ignite will fit my use case (I hope so). It seems to have all of the aspects I am looking for.

I am trying to do the f= ollowing:
  • I am building up a realtime analytics / business dashboard based on a whole lot of metrics and messages in the integration space (utilising something like a time series database).=C2=A0
  • I would like to stream messages from a number of different data collectors (I am using queues at the moment for this task)
    • At the moment I am putting these messages into Graylog / Elasticsearch but I am looking to change this
  • I need to store the time series data in a DB (About 1-5 million messages a day)
    • I want to evict / delete the data after a month or so (if space is a problem)=C2=A0
    • I need to do some basic aggregation and CEP
  • I would like to aggregate the data over time (and thus reduce the granularity / size)

I guess my questions are the following:
  • Can I start using Ignite (in a single (or a few) nodes initially) as a SQL / KV store (I will probably persist the data to disk very soon only keeping a few 10-20GB in RAM and use it more like a traditional =E2=80=9CDB=E2=80=9D)?
Yes, the documentation section below explains how to define how much memory to dedicate in RAM and how to enable the persistence:
  • My concern is the Ignite was not designed for this (as it seems mostly in memory) so I am unsure about how it will work persisting 500-1000GB of data on a single node (I guess I am trying to use it more as a hybrid in memory store)
Ignite 2.x is based on a completely new memory architecture where disk stores a subset of data and RAM caches as much data as you can afford.
https://apacheignite.readme.io/docs/durable-memory
So, presently Ignite is also used as a system of records or classical DB.

  • The documentation seems to refer to using it as a cache in front of a RDBMS but I would like to just use Ignite as the only DBMS
What=E2=80=99s the documentation you=E2=80=99re referring to? There are man= y documentation and use cases pages Ignite is used for.

For instance, the use cases on the site unveil how to use it as a DBMS:
https:/= /ignite.apache.org/usecases.html
  • Can I aggregate the data using time as a =E2=80=9Cgrouping&q= uot; field ?
    • I will delete the expired data from the db periodically
    • I want to do CEP on the data

Yes

Denis
Thanks for the help in advance.

Regards
Steve

--94eb2c1b50baf86ea505601444d3--