Holy crap :)

Was able to reproduce this. The problem appears to be that we've upgraded
the version of the round robin database that we use to store server
statistics. The new RRDB finds the old 1.2 data file (it's
[server]/data/graph.db/rrd) and happily parses it, but interprets it in
crazy ways.

As a direct fix for this, turn off your server and then backup and delete
the rrd file. The server will create a new one upon startup with the correct
format.

I'll have to look into what we can do to mitigate this - we'll make sure to
document it at the least, but ultimately this upgrade should be possible
without having to lose all previous monitoring data..

Thank you for taking the time to bring it to our attention!
/Jake

On Wed, Mar 16, 2011 at 5:13 PM, neo4j.org <nore...@neo4j.org> wrote:

> #323: Dashboard charts show wrong number of primitives after 1.3 migration
>
> -----------------------------+----------------------------------------------
>  Reporter:  bnor...@drw.com  |       Owner:  peter
>     Type:  bug report       |      Status:  new
>  Priority:  major            |   Milestone:
> Component:  server           |    Keywords:  1.3.M04
>
> -----------------------------+----------------------------------------------
>  I upgraded a 1.2 graph to 1.3.M04 using the special upgrade instructions
>  at http://docs.neo4j.org/chunked/milestone/deployment-upgrading.html . I
>  have 4858 nodes in this graph, but the chart is using a scale of 10^307
>  for the y-axis. The attached screenshot will illustrate the entertainment
>  value therein. ;-)
>
> --
> Ticket URL: <https://trac.neo4j.org/ticket/323>
> neo4j.org <http://trac.neo4j.org/>
> The Neo4J.org Issue Tracker
> _______________________________________________
> Tickets mailing list
> tick...@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/tickets
>



-- 
Jacob Hansson
Phone: +46 (0) 763503395
Twitter: @jakewins
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to