Weird chat grouping

[c0fe]

I got weird chat grouping. Here is what I mean:

You see that it isn't publishing the talk as in a regular chat fashion

Person A: Blah Blah
Person B: Blah Blah Blah
Person A: Blah Blah Blah Blah
Person A: Blah Blah Blah

But it is grouping them strangely. How can I get it to show up in more regular format?

[klatys]

There's a setting for that. See administration > Message > Grouping Period (in seconds)
Grouping Period (in seconds)

[geekgonecrazy]

See @klatys 's suggestion. That will help with grouping.

As far as the messages get out of order. That might be a problem. But we're going to need a bit more information.

• Browser
• Server Version
• Deployment method
• Steps to reproduce

[meltenc]

Hi,

We experienced the same issue and even a worse behaviour because some messages were grouped on the wrong guy !

So we had three issues probably related to the same bug :

• Some messages sent after another message appear before it.
• Some messages are getting grouped to the wrong sender.
• Two messages are getting grouped to the good sender even if someone has already posted a message between those two messages.

Reproduced on mac os client, with version 0.35 deployed with rancher (ie with docker)

[c0fe]

Browser: Chrome (up to date)
Server: Debian 8 (all updates installed)
Deployment: Regular Node.JS, no Docker

[meltenc]

I have just found that the issue came from our load balancer, with only one instance of rocket everything went back to normal.
Sorry for the inconvenience.

[geekgonecrazy]

@Throll this is very useful information. @cofe are you running multiple instances as well?

[c0fe]

No, only one instance. The server is dedicated to Rocket Chat

[geekgonecrazy]

I've actually seen this several times as well lately. I've sent messages after someone else, and it grouped my messages as if they came from the previous poster.

I'm thinking this has something to do with timestamps.

[meltenc]

FYI Our issue did not come from our load balancer but our 2 instances were not time synchronized.

[geekgonecrazy]

@Throll that makes perfect sense. Would probably result in messages being in wrong order and etc also. Your case is something we need to add in our high availability documentation.