Hi,
I am wondering if there is a clearly explanation or docs somewhere that
explains a little bit more on what some of the /stats represent.
Also which are the ones you would want your sysadmin to watch / monitor closely.
Thanks.
- Jon
___
riak-us
Double checked and yes that's sorted by Stack+heap. There's two ets
tables that are 8 and 9mb respectively and that's all I can find for
memory usage. Anywhere else I can look for the culprit if it's not a
process or ets table?
On Fri, Jul 8, 2011 at 5:20 PM, Dan Reverri wrote:
> The Stack+heap
The Stack+heap for that process is only ~0.17 GB which isn't that much. Are
you sorting the process list by Reductions or Stack+heap?
Regarding the messages in queue, I think you should be able to explore each
Pid and look at it's process dictionary. The process dictionary will have a
messages pro
Thanks Dan, very useful tool. Here's the big offender:
Pid Name/Spawned as State Reductions Stack+heap MsgQ
Length
<0.163.0> riak_kv_map_master Garbing (limited info) 23815122240
182452560 3
So it looks like there was a huge amount of data in the p
Can you check if an erl_crash.dump file was created? The crash dump should give
some indication of which processes were taking up memory.
The crashdump_viewer built into Erlang is very useful for reviewing crash
dumps.
Thanks
Dan
Sent from my iPhone
On Jul 8, 2011, at 4:18 PM, Sylvain Niles
Our system had been humming along fine for a week and crashed today
with almost no load. This is the only thing in the erlang.log:
=INFO REPORT 8-Jul-2011::16:46:14 ===
[{alarm_handler,{clear,system_memory_high_watermark}}]
=INFO REPORT 8-Jul-2011::16:50:14 ===
[{alarm_handler,{set,{syste
Phil,
Sorry for the troubles this morning, I went ahead and updated the version of
rebar currently on riak/master. We are working on a different (and better)
method of dealing with rebar being packaged in our repositories.
Thanks,
Jared
.
On Fri, Jul 8, 2011 at 12:41 PM, Phil Stanhope wrote:
Afternoon, Evening, Morning to All -
For today's Recap: A new release for the Haskell client, new code, a
Ripple Hackathon, and more.
Enjoy and have a great weekend.
Mark
Community Manager
Basho Technologies
wiki.basho.com
twitter.com/pharkmillups
Riak
Thanks Sean.
I did what you suggested. Pulled and built a new rebar. Copied that into
/usr/local/bin. Checked that it would take precedence over the one that is
packaged in the RIAK repo.
The one in the root of RIAK is "rebar version: 2 date 20110310_184739
2e1b4da". The newly built one is: "reba
Phil,
This is a question best sent to the riak-users list. Recent changes in the
codebase necessitate an upgrade to rebar. In your source checkout, download
rebar from here: https://github.com/downloads/basho/rebar/rebar ... then
re-attempt the build.
On Fri, Jul 8, 2011 at 2:01 PM, Phil Stanho
(1) AIUI a given key/value data pair is "owned" by a given node at one time
and operations on it happen on that node and are then replicated out. Is
this correct?
(2) Is the key/value pair "locked" between pre update and post update?
The motivation for this question is this.
I need to do the fo
(1) AIUI a given key/value data pair is "owned" by a given node at one time
and operations on it happen on that node and are then replicated out. Is
this correct?
(2) Is the key/value pair "locked" between pre update and post update?
The motivation for this question is this.
I need to do the fo
Hi Carlo,
>From the error report it looks like riak was having problems opening a file
in the /tmp/riak/slide-data directory. Do you have any processes that clean
up temporary files / dirs while riak is running?
BR, Jon.
On Thu, Jul 7, 2011 at 2:32 AM, Carlo Bertoldi
wrote:
> Hello everybody,
> If you have any doubt, *always* prefer `db.get()` and `db.save()`. I
> kinda regret having agreed to include `db.update()`. If it's causing
> confusion I will have to remove it.
I changed it to a db.get() and db.save() and it works (using express):
app.post('/users/save', function(req, res) {
14 matches
Mail list logo
