Hi Malcolm,
Questions:
> 1. In the future, what kind of diagnostic information (memory, processes,
> etc.) can I provide to help resolve issues? Are there specific linux
> commands I should execute and provide results?
>
In such cases (recovery procedure failure) the root of the problem usually
can be found if it's possible to reproduce crash (or unexpected shutdown-
process kill or machine reboot) of the database wich caused restart with
recovery. So, what can we actually try? We can try to get your source data
(XML files), your workload (queries, updated from event logs), try to rerun
and crash (kill) Sedna until we get recovery failure.
Ideally, if you know steps from the very beginning how to reproduce it we
can fix the bug very soon.
> 2. Is the root cause a Linux or Sedna configuration problem, or is the
> problem a Sedna DB issue?
>
Most likely it's DB issue.
> 3. Is there any configuration that would be considered optimal for an
> Amazon micro-instance that has nothing but Senda as the core process? The
> DB can grow to 6 GB, number of required simultaneous connections is
> limited,
> maybe 10 max. I don't mind recompiling code if that helps. (I think I
> have
> asked this question before, sorry for being repetitive.)
>
Just make sure that you don't use too big buffers number value. It doesn't
make sense to use 1GB buffers if instance has 600MB ram. Remeber that OS
also needs some memory for cache, for system processe, etc. I would try to
use 400MB at first monitoring response times.
4. I noticed that Sedna build is up to build 3.5.13. Are there any good
> reasons to move from 3.4.66 to the latest build? Are there any stable
> builds since the 3.4.66 release?
>
No. Though 3.5 will be released soon. Don't use it now. It still has minor
issues.
> I have all the data associated with db stored elsewhere, so I am going to
> simply rebuild the instance and move on. I just want to do my best from
> having the issue occur again.
>
We also want to make it reliable as much as possible. Unfortunatelly,
recovery failure is very hard to debug. We really need help from DB users to
investigate/reproduce this problem to fix it.
Ivan Shcheklein,
Sedna Team
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
