XenForo Do you use XFES/Elasticsearch? (1 Viewer)

[Cedric]

ES is great when it works. It may be my setup (although done correctly, as far as I know) my ES connection fails every undefined amount of time. Then I need to log in, restart the ES and then it works again. Annoying.

 

[Arantor]

ES is great when it works. It may be my setup (although done correctly, as far as I know) my ES connection fails every undefined amount of time. Then I need to log in, restart the ES and then it works again. Annoying.

How much memory is it using? Are there any signs in the log that it's the system killing it due to memory consumption? (this is a common issue with ES, as above)

 

[Cedric]

How much memory is it using? Are there any signs in the log that it's the system killing it due to memory consumption? (this is a common issue with ES, as above)

I've got 16gb memory, so I doubt it's due that. And last time I checked, there was nothing in the logs either. It's quite weird.

 

[frm]

I've got 16gb memory, so I doubt it's due that. And last time I checked, there was nothing in the logs either. It's quite weird.

This likely isn't the issue, but sometimes even the best of us can overlook a simple setting (like I did with not checking an auto-backup checkbox).

Are you running it in Docker and has your system ever rebooted that you know of, manual or automatic (what is uptime)? I don't know how it's set up outside of Plesk (the docker-compose.yml configuration), but there is this checkbox...


"Automatic start after system reboot"

Could be your instance rebooting from cluster maintenance to you doing a manual reboot to a system upgrade rebooting it automatically, but it happens so quickly you don't notice, thus knocking it offline if it's not set to start after a reboot.

 

[Cedric]

This likely isn't the issue, but sometimes even the best of us can overlook a simple setting (like I did with not checking an auto-backup checkbox).

Are you running it in Docker and has your system ever rebooted that you know of, manual or automatic (what is uptime)? I don't know how it's set up outside of Plesk (the docker-compose.yml configuration), but there is this checkbox...
View attachment 380

"Automatic start after system reboot"

Could be your instance rebooting from cluster maintenance to you doing a manual reboot to a system upgrade rebooting it automatically, but it happens so quickly you don't notice, thus knocking it offline if it's not set to start after a reboot.

My system has no reboot that I know of.

A simple restart usually does the trick though. I just can't figure out why it stops working in the first place. There's no consistency either. Sometimes it takes days, sometimes weeks.

 

[frm]

My system has no reboot that I know of.

A simple restart usually does the trick though. I just can't figure out why it stops working in the first place. There's no consistency either. Sometimes it takes days, sometimes weeks.

What version of ES are you using and in Docker or a standalone installation?

I'd try pulling the Docker 7.10.2 version. Easiest configuration and have had no problems.

Quite odd to fail on 16GB RAM multiple times while ES7 given only 1GB has more uptime.

 

[Cedric]

What version of ES are you using and in Docker or a standalone installation?

I'd try pulling the Docker 7.10.2 version. Easiest configuration and have had no problems.

Quite odd to fail on 16GB RAM multiple times while ES7 given only 1GB has more uptime.

Standalone, version 10-something. The latest in any case.

And in any case, my VPS is a bit over spec'ed for what I need, but I figured, the more space/memory you have, the better.

 

[frm]

And in any case, my VPS is a bit over spec'ed for what I need, but I figured, the more space/memory you have, the better.

Ah, the "my truck is bigger than your truck" way of thinking.

I like to use the most minimal settings possible and then scale up when needed. It's quite easy to monitor what is needed and when and then scale up to support that.

Though, I would love to learn more about AWS and Cloud in general to not scale up permanently, until absolutely needed, and instead launch a new instance to load balance instead, destroying it when it's no longer needed. I haven't gotten around to testing that, nor have enough traffic to try as 2 vCPU/2 GB has no problem struggling with what I have, and have only ever gotten to the point of requiring 4 vCPU/8 GB RAM (but also used that instance for personal use as a VPN amongst other things, which I no longer do as I'm incorporating finally and that makes it kind of messy with finances). I would probably do it on 1 vCPU/1 GB RAM to test and learn at first before requiring true minimum spec requirements to load balance with.

 

[Cedric]

Ah, the "my truck is bigger than your truck" way of thinking.

I like to use the most minimal settings possible and then scale up when needed. It's quite easy to monitor what is needed and when and then scale up to support that.

Though, I would love to learn more about AWS and Cloud in general to not scale up permanently, until absolutely needed, and instead launch a new instance to load balance instead, destroying it when it's no longer needed. I haven't gotten around to testing that, nor have enough traffic to try as 2 vCPU/2 GB has no problem struggling with what I have, and have only ever gotten to the point of requiring 4 vCPU/8 GB RAM. I would probably do it on 1 vCPU/1 GB RAM to test and learn at first before requiring true minimum spec requirements to load balance with.

Yes. Sadly that is a bit true. I’m also desperately afraid of running out of resources one day. Waking up, to see my server being offline or overwhelmed. I know that isn’t likely to happen overnight (unless a technical failure) but I’m honestly not fussed about it being over-spec’ed. It’s costing me a little over 40USD a month, so..

 

[frm]

Waking up, to see my server being offline or overwhelmed.

That's a worry of mine too, as to why I want to learn load balancing.

I think it's even possible to see where you're getting the most traffic (like US: East or West coast, Canada, UK, or Aussie, etc.) and load balancing judges based on that to pop an instance up in that location so that the processing speeds aren't only better, but response times too. Someone with more knowledge would have to correct me on that, but if that's true, that is one of the most awesome aspects I find with it.