Chat - eMediaLibrary Project

General

Page 95 of 129

Christopher B 3/15/24, 2:53:17 PM EDT

Need help? I am in the dev zoom

Cristobal M 3/15/24, 2:54:07 PM EDT

Restarted the nodes, and launched the missing generated, good news is new Assets are being converted as they arrive

Cristobal M 3/15/24, 2:54:19 PM EDT

but I think the missing generated is gonna take a while, 200K assets

Christopher B 3/15/24, 2:54:33 PM EDT

On production?

Cristobal M 3/15/24, 2:54:42 PM EDT

in their side, they are trying to figureit out when the 3rd node came online
yes, this is Prod.

Christopher B 3/15/24, 2:55:01 PM EDT

We really should run with 3 nodes I think

Christopher B 3/15/24, 2:55:18 PM EDT

I never understood why we would not want that

Cristobal M 3/15/24, 2:55:24 PM EDT

yes, but they used to have that 3rd server offline

Christopher B 3/15/24, 2:55:33 PM EDT

Why?

Cristobal M 3/15/24, 2:55:38 PM EDT

It was originally like that, then the 3rd carashed

Cristobal M 3/15/24, 2:56:07 PM EDT

I donnt know, like something internal with their IT providers

Christopher B 3/15/24, 2:57:59 PM EDT

Not a good answer. We need to know what is happening with production

Cristobal M 3/15/24, 2:58:55 PM EDT

we don't manage the servers, they told us they can not put it back online and Production was running with 2 nodes for a while

Cristobal M 3/15/24, 3:05:46 PM EDT

Fix missing generated, scans all the assets table and starts with conversions until finishes scanning?

Christopher B 3/15/24, 3:43:45 PM EDT

it checks if the files are there or not

Cristobal M 3/15/24, 4:30:23 PM EDT

Ok, issue solved. They ran into one of those Deploy they used to do, and one of the batches got stuck at the end of their tests. This was caused for a particular asset, I was able to find it and download it, tested locally and exact same issue happens in current version. There is a bug in GeoLocation metadata extractor, it fails with: Caused by: java.lang.IllegalArgumentException: illegal latitude value [2.18327504213333E9] for geo_point at org.elasticsearch.index.mapper.geo.GeoPointFieldMapper.parse(GeoPointFieldMapper.java:123) I guess is for the E9 at the end of the string? All right, that is the bug, but that was stuck on all metadata-readings, so the script every time gets to this assets fails and I'll guess is not saving the batch of assets? and then start again the same batch and then got stuck. Probably another bug here. The other issue it was: Yest 189 came back, they had an upgrade of their VM recently, so that may came back to life in that time. Elasticsearch find it and attache it to the Cluster, which is 100% Green with 3 nodes running right now. So we are back to the originally architecture we asked for. Last: They are interested in re-take conversations about Archiving assets, they got their new VMS with 8-core and 12T volumes (they have 3T available) but the want to do some type of archiving to improve speed and conversion times, they are good with the Hard drive for now. So they are open to meet with you some time middle of next week if possible.

Cristobal M 3/15/24, 4:31:54 PM EDT

I'll keep an eye in the cluster and pending conversions this days but at least the batch of assetts they where waiting for it is done now. Their current version has some JS issue it was really difficult to multi-select, so I ended up requeing about 80 assets by hand.
Ok, brb.