Description of problem: Too many logs of creating bricks status file in geo-rep logs. Within the time interval of 1 and half hours, there were ~200 occurrence of these logs in geo-rep log. Version-Release number of selected component (if applicable):glusterfs-3.4.0.57rhs-1 How reproducible: Have observed this earlier also, not easy to reproduce. Steps to Reproduce: 1. create and start a geo-rep relationship between master and slave. 2. keep creating data on master. 3. check for the below logs Actual results: geo-rep logs keep getting lot of "creating bricks status file" Expected results: There might be some problem with this. Once created, it shouldn't keep creating status file. Additional info: sample logs >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2014-01-15 13:53:29.209451] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:32.215740] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:32.218713] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:32.221036] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:32.223287] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:32.225418] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:35.235112] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:35.237489] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:35.240191] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:35.242492] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:38.252830] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:38.255168] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:38.257347] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:53:47.294991] I [master(/bricks/master_brick1):451:crawlwrap] _GMaster: 20 crawls, 0 turns [2014-01-15 13:54:02.378454] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:54:02.380697] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status [2014-01-15 13:54:02.382602] I [master(/bricks/master_brick1):918:update_worker_status] _GMaster: Creating new /var/lib/glusterd/geo-replication/master_10.70.43.76_slave/_bricks_master_brick1.status >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Geo-replication Status infrastructure is improved in RHGS 3.1 and this issue is not seen during regression runs of RHGS 3.0.4 and RHGS 3.1. Closing this bug. Please reopen if this issue found again.