Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 4 Mar 2015 00:00:13 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12746343.1412668962000.69954.1425427213942@Atlassian.JIRA>
In-Reply-To: <JIRA.12746343.1412668962000@Atlassian.JIRA>
References: <JIRA.12746343.1412668962000@Atlassian.JIRA>
 <JIRA.12746343.1412668962144@arcas>
Subject: [jira] [Commented] (CASSANDRA-8067) NullPointerException in
 KeyCacheSerializer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346035#comment-14346035 ] 

Benedict commented on CASSANDRA-8067:
-------------------------------------

Eh, it's not a burning desire to make better, so I'll leave it thanks. More than enough to do. A brief handwavy outline is that the current abstraction adds complexity by not really separating concerns; the duplication is not a problem of the cost of the work but of the cognitive burden (which is essentially why this happened in the first place). But since it's not a significant pain point, it's not worth agonising over either. 

> NullPointerException in KeyCacheSerializer
> ------------------------------------------
>
>                 Key: CASSANDRA-8067
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8067
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Eric Leleu
>            Assignee: Aleksey Yeschenko
>             Fix For: 2.1.4
>
>         Attachments: 8067.txt
>
>
> Hi,
> I have this stack trace in the logs of Cassandra server (v2.1)
> {code}
> ERROR [CompactionExecutor:14] 2014-10-06 23:32:02,098 CassandraDaemon.java:166 - Exception in thread Thread[CompactionExecutor:14,1,main]
> java.lang.NullPointerException: null
>         at org.apache.cassandra.service.CacheService$KeyCacheSerializer.serialize(CacheService.java:475) ~[apache-cassandra-2.1.0.jar:2.1.0]
>         at org.apache.cassandra.service.CacheService$KeyCacheSerializer.serialize(CacheService.java:463) ~[apache-cassandra-2.1.0.jar:2.1.0]
>         at org.apache.cassandra.cache.AutoSavingCache$Writer.saveCache(AutoSavingCache.java:225) ~[apache-cassandra-2.1.0.jar:2.1.0]
>         at org.apache.cassandra.db.compaction.CompactionManager$11.run(CompactionManager.java:1061) ~[apache-cassandra-2.1.0.jar:2.1.0]
>         at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[na:1.7.0]
>         at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) ~[na:1.7.0]
>         at java.util.concurrent.FutureTask.run(Unknown Source) ~[na:1.7.0]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.7.0]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.7.0]
>         at java.lang.Thread.run(Unknown Source) [na:1.7.0]
> {code}
> It may not be critical because this error occured in the AutoSavingCache. However the line 475 is about the CFMetaData so it may hide bigger issue...
> {code}
>  474             CFMetaData cfm = Schema.instance.getCFMetaData(key.desc.ksname, key.desc.cfname);
>  475             cfm.comparator.rowIndexEntrySerializer().serialize(entry, out);
> {code}
> Regards,
> Eric


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