[Gluster-users] warning spam in the logs after tiering experiment

[Dmitri Chebotarov]

Hi Alastair

I apologize my email is off topic, but I also have strange issues on a
volume and it happened to be volume with hot-tier attached to it in past.

Can you do me a favor and test something on the volume where you used to
have hot-tier?

I'm working with RH on issue where glusterfs fuse client crashes while
doing 'grep' on files.

Here are the steps:

On the volume where you had hot-tier enabled:

# generate dataset for testing:

mkdir uuid-set; cd uuid-set
for i in $(seq 40); do uuidgen | awk {'print "mkdir "$1"; echo test >>
"$1"/"$1".meta"'}; done | sh

# run grep

grep test */*.meta

#Running 'grep' may crash glusterfs-client. If it doesn't crash, do the
following:

rsync -varP uuid-set/ uuid-set2
grep test uuid-set2/*/*.meta

Thank you.

On Wed, Oct 18, 2017 at 1:27 PM, Alastair Neil <ajneil.tech at gmail.com>
wrote:

> forgot to mention Gluster version 3.10.6
>
> On 18 October 2017 at 13:26, Alastair Neil <ajneil.tech at gmail.com> wrote:
>
>> a short while ago I experimented with tiering on one of my volumes.  I
>> decided it was not working out so I removed the tier.  I now have spam in
>> the glusterd.log evert 7 seconds:
>>
>> [2017-10-18 17:17:29.578327] W [socket.c:3207:socket_connect] 0-tierd:
>> Ignore failed connection attempt on /var/run/gluster/2e3df1c501d0a19e5076304179d1e43e.socket,
>> (No such file or directory)
>> [2017-10-18 17:17:36.579276] W [socket.c:3207:socket_connect] 0-tierd:
>> Ignore failed connection attempt on /var/run/gluster/2e3df1c501d0a19e5076304179d1e43e.socket,
>> (No such file or directory)
>> [2017-10-18 17:17:43.580238] W [socket.c:3207:socket_connect] 0-tierd:
>> Ignore failed connection attempt on /var/run/gluster/2e3df1c501d0a19e5076304179d1e43e.socket,
>> (No such file or directory)
>> [2017-10-18 17:17:50.581185] W [socket.c:3207:socket_connect] 0-tierd:
>> Ignore failed connection attempt on /var/run/gluster/2e3df1c501d0a19e5076304179d1e43e.socket,
>> (No such file or directory)
>> [2017-10-18 17:17:57.582136] W [socket.c:3207:socket_connect] 0-tierd:
>> Ignore failed connection attempt on /var/run/gluster/2e3df1c501d0a19e5076304179d1e43e.socket,
>> (No such file or directory)
>> [2017-10-18 17:18:04.583148] W [socket.c:3207:socket_connect] 0-tierd:
>> Ignore failed connection attempt on /var/run/gluster/2e3df1c501d0a19e5076304179d1e43e.socket,
>> (No such file or directory)
>>
>>
>> gluster volume status is showing the tier daemon status on all the nodes
>> as 'N', but lists the pids of a nonexistent processes.
>>
>> Just wondering if I messed up removing the tier?
>>
>> -Alastair
>>
>>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171018/04d09eef/attachment.html>