Bug 1467536 - Seeing timer errors in the rebalance logs
Seeing timer errors in the rebalance logs
Status: ON_QA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rpc (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: RHGS 3.4.0
Assigned To: Mohit Agrawal
Rahul Hinduja
Depends On: 1538427 1542934
Blocks: 1503134
  Show dependency treegraph
Reported: 2017-07-04 03:21 EDT by Prasad Desala
Modified: 2018-02-24 05:22 EST (History)
7 users (show)

See Also:
Fixed In Version: glusterfs-3.12.2-4
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1538427 1542934 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Prasad Desala 2017-07-04 03:21:53 EDT
Description of problem:
I have seen below timer error in rebalance logs after remove-brick completion,
however I didn't see any functionality impact here, remove-brick rebalance completed without any failures.

[2017-07-04 05:34:58.215846] W [glusterfsd.c:1290:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7e25) [0x7f07e0176e25] -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x561a54853005] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x561a54852e2b] ) 0-: received signum (15), shutting down
[2017-07-04 05:34:58.220109] I [timer.c:212:gf_timer_registry_init] (-->/lib64/libglusterfs.so.0(+0x3782d) [0x7f07e132482d] -->/lib64/libgfrpc.so.0(+0xfac3) [0x7f07e10dfac3] -->/lib64/libglusterfs.so.0(gf_timer_call_after+0x215) [0x7f07e1324b65] ) 0-timer: ctx cleanup started
[2017-07-04 05:34:58.220307] E [timer.c:44:gf_timer_call_after] (-->/lib64/libglusterfs.so.0(+0x3782d) [0x7f07e132482d] -->/lib64/libgfrpc.so.0(+0xfac3) [0x7f07e10dfac3] -->/lib64/libglusterfs.so.0(gf_timer_call_after+0x25b) [0x7f07e1324bab] ) 0-timer: !reg
[2017-07-04 05:34:58.220352] W [rpc-clnt.c:168:call_bail] 0-glusterfs: Cannot create bailout timer for

Version-Release number of selected component (if applicable):

How reproducible:
Reporting the first occurrence.

Steps to Reproduce:
1) Create a distrbuted-replicate volume and start it.
2) cifs mount the volume on multiple clients.
3) From client-1 -> start creating files and from a diff terminal start continuous lookups.
   wait for some time and from client-2 -> Start creating hardlinks
4) Remove few bricks and wait till the remove-brick operation completes.

After completion of remove-brick, check rebalance logs and you will see above timer error messages.

Actual results:
Seeing timer errors in rebalance logs.

Expected results:
No timer error messages should come in rebalance logs.

Note You need to log in before you can comment on or make changes to this bug.