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 11873200C00 for ; Wed, 4 Jan 2017 01:00:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1020E160B49; Wed, 4 Jan 2017 00:00:00 +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 7E00F160B43 for ; Wed, 4 Jan 2017 00:59:59 +0100 (CET) Received: (qmail 29672 invoked by uid 500); 3 Jan 2017 23:59:58 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 29641 invoked by uid 99); 3 Jan 2017 23:59:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2017 23:59:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 691282C0453 for ; Tue, 3 Jan 2017 23:59:58 +0000 (UTC) Date: Tue, 3 Jan 2017 23:59:58 +0000 (UTC) From: "Ewen Cheslack-Postava (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (KAFKA-4579) Schema Registry client should have a proper caching mechanism for schema IDs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 04 Jan 2017 00:00:00 -0000 [ https://issues.apache.org/jira/browse/KAFKA-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4579. ------------------------------------------ Resolution: Invalid Assignee: Ewen Cheslack-Postava Closing as this should be filed against the schema-registry project. > Schema Registry client should have a proper caching mechanism for schema IDs > ---------------------------------------------------------------------------- > > Key: KAFKA-4579 > URL: https://issues.apache.org/jira/browse/KAFKA-4579 > Project: Kafka > Issue Type: Bug > Components: clients > Affects Versions: 0.10.1.1 > Environment: Kafka version: 10.0.1 > JVM: 1.8 > OS: Ubuntu 14.01 LTS > Reporter: Justin Manchester > Assignee: Ewen Cheslack-Postava > > Problem: > Currently the Schema Registry client does not have a proper caching mechanism for Schema IDs. This regularly leads to users writing producers which do not reuses schema ID's and which then crash with the following: > Caused by: java.lang.IllegalStateException: Too many schema objects created > Suggested solution: It would better if we had a proper caching mechanism in place to prevent hard crashes. This often leads to data loss, and the concept of reusing schema ID's is not always intuitive to users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)