Mailing-List: contact commits-help@sentry.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sentry.incubator.apache.org
Date: Fri, 19 Feb 2016 06:22:18 +0000 (UTC)
From: "Anne Yu (JIRA)" <jira@apache.org>
To: commits@sentry.incubator.apache.org
Message-ID: <JIRA.12940395.1455862894000.90789.1455862938082@Atlassian.JIRA>
In-Reply-To: <JIRA.12940395.1455862894000@Atlassian.JIRA>
References: <JIRA.12940395.1455862894000@Atlassian.JIRA>
 <JIRA.12940395.1455862894103@arcas>
Subject: [jira] [Created] (SENTRY-1083) Improve sentry cache (server,
 client) by using a stable commercial or main-strain cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Anne Yu created SENTRY-1083:
-------------------------------

             Summary: Improve sentry cache (server, client) by using a stable commercial or main-strain cache 
                 Key: SENTRY-1083
                 URL: https://issues.apache.org/jira/browse/SENTRY-1083
             Project: Sentry
          Issue Type: New Feature
          Components: Sentry
    Affects Versions: 1.7.0
            Reporter: Anne Yu


We've seen many unreproducible issues because the sentry caches (either server side or client/plugin side) are full, or out of sync; We could start to consider a main-stream or open source cache to use across sentry project. The benefit of a widely used cache system:

1. has basic monitoring or dump facility;
2. has useful logging system;
3. usually is very high performanced in the memory;

I know for example, kafka incorporate RocksDb ([code example|https://github.com/apache/kafka/blob/trunk/gradle/dependencies.gradle#L39]).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)