Found the following in the dmesg. Maybe I've hit a bug?
INFO: task java:18056 blocked for more than 120 seconds.
Not tainted 2.6.32-431.3.1.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
java D 0000000000000002 0 18056 1 0x00000080
ffff883fe016fdc8 0000000000000082 0000000000000000 ffff883fe016fde8
ffff883fe016fd88 ffffffff8111f3f0 ffff881a89bc25d8 ffff883fe016fde8
ffff883edb4025f8 ffff883fe016ffd8 000000000000fbc8 ffff883edb4025f8
Call Trace:
[<ffffffff8111f3f0>] ? find_get_pages_tag+0x40/0x130
[<ffffffff8109b5de>] ? prepare_to_wait+0x4e/0x80
[<ffffffffa00775a5>] jbd2_log_wait_commit+0xc5/0x140 [jbd2]
[<ffffffff8109b2b0>] ? autoremove_wake_function+0x0/0x40
[<ffffffff81134ca1>] ? do_writepages+0x21/0x40
[<ffffffffa0077938>] jbd2_complete_transaction+0x68/0xb0 [jbd2]
[<ffffffffa0093231>] ext4_sync_file+0x121/0x1d0 [ext4]
[<ffffffff811baa71>] vfs_fsync_range+0xa1/0x100
[<ffffffff811bab3d>] vfs_fsync+0x1d/0x20
[<ffffffff811bab7e>] do_fsync+0x3e/0x60
[<ffffffff811babd0>] sys_fsync+0x10/0x20
[<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
Op dinsdag 26 augustus 2014 14:54:50 UTC+2 schreef R. Toma:
>
> Hi all,
>
> In an attempt to squeeze more power out of our physical servers we want to
> run multiple ES jvm's per server.
>
> Some specs:
> - servers has 24 cores, 256GB ram
> - each instance binds on different (alias) ip
> - each instance has 32GB heap
> - both instances run under user 'elastic'
> - limits for 'elastic' user: memlock=unlimited
> - es config for both instances: bootstrap.mlockall=true
>
> The 1st instance has been running for weeks.
>
> When starting the 2nd instance the following things happen:
> - increase of overal cpu load
> - lots of I/O to disks
> - no logging for 2nd instance
> - 2nd instance hangs
> - 1st instance keeps running, but gets slowish
> - cd /proc/<pid> causes a hang of cd process (until 2nd instance is killed)
> - exec 'ps axuw' causes a hang of ps process (until 2nd instance is killed)
>
> Maybe (un)related: I have never been able to run Elasticsearch in a
> virtualbox with memlock=unlimited and mlockall=true.
>
>
> After an hour of trial & errors I found that removing setting
> 'bootstrap.mlockall' (setting it to false) from 2nd instance's
> configuration fixes things.
>
> I am confused, but acknowledge I do not know anything about memlocking.
>
> Any ideas?
>
> Regards,
> Renzo
>
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/7fc4566e-631d-49f7-b012-3d1c2270102f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
