[Bug][ARM] Missing re2 ARM build cause Internal Server Error

[ananzh]

Describe the bug

Currently, re2 doesn't have an ARM build. When run osd in graviton instance, we observe the following error:

node_modules/re2/build/Release/re2.node: cannot open shared object file: No such file or directory

To Reproduce

• Use a graviton2 instance (Linux aarch64)

• logon to OSD

• load sample web log data

• go to visualize and select to create a timeline visualization

• type in query .es(split=host.keyword:50, index=opensearch_dashboards_sample_data_logs).label("Host Name: $1", "^.:(.) >.*")

Expected behavior
Solve the above error

OpenSearch Version
1.0.0

Dashboards Version
1.0.0

Host/Environment (please complete the following information):

• OS: Linux aarch64

[ananzh]

To solve this issue, we need to modify the native modules here and add similar url and sha256 for linux-arm64

Some steps to solve:

1. create linux-arm64-64.gz

npm install --save re2
cd node_modules/re2
gzip -c build/Release/re2.node > linux-arm64-64.gz

2. upload to a storage place and provide url and sha256 in this issue
3. we will then patch it in the code

need some here from infra @bbarani @peterzhuamazon

[kavilla]

Should we close this issue: #648

[ananzh]

Should we close this issue: #648

O sorry. I think it is duplicate. I will close this one.

[kavilla]

Moving to 1.2 label since we still do not have a replacement artifact.

[ananzh]

@bbarani @peterzhuamazon @peternied

To solve this issue, we need to modify the native modules here and add similar url and sha256 for linux-arm64

Some steps to solve:

1. create linux-arm64-64.gz

npm install --save re2
cd node_modules/re2
gzip -c build/Release/re2.node > linux-arm64-64.gz

1. upload to a storage place and provide url and sha256 in this issue
2. we will then patch it in the code

@bbarani @peterzhuamazon @peternied Haven't heard back and let me make the request more clearly. To solve this reported issue and allow re2 to have a ARM64 build, we need to have a re2.node uploaded and saved. I think the Infra team could help here to apply step 1 to create linux-arm64-72.gz and help to save it to a place that is able to be referred. Then Dashboards can update the patch_native_modules_task.ts to verify again whether it solves the problem.

[peterzhuamazon]

We need more context on this one:

1. What is this re2 used for?
2. Is it a native plugin for Dashboards and you already have your code ready for arm64?
3. How did you resolve the x64 cases and urls? I dont think Infra has done anything to provide the x64 one.
4. Is this related to a plugin or anything? If not, then it should be part of the Dashboards build itself handled by your team I think.

Thanks.

[kavilla]

Hi @peterzhuamazon

This for the timeline core plugin. This bug existed pre-fork with the error message including: node_modules/re2/build/Release/re2.node: cannot open shared object file: No such file or directory. It turns out the application uses node-re2 so that it can safely use the regular expressions specified by end-users within Timeline, but Node-RE2 does not contain a hosted build for ARM. So it fails while hosted on machines with ARM architecture since it doesn't exist. So the proposed solution would to be place where it is hosted but perhaps we can just download a version and throw it into the repo.

[ananzh]

@peterzhuamazon
A bit more comments here:
Here is the list of NODE-RE2 hosted build and you could see there is no ARM. Kibana solved this issue by manually created it (could use my steps as reference) and host it here in https://storage.googleapis.com. So we are seeking some help to host it.

[peterzhuamazon]

similar to chromium no arm64 version cause percy agent to complain when build on arm64?