Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BIGTOP-3763: Fix Hive build issues about protobuf 2.5.0 on Arm64 and PPC64le #970

Merged
merged 2 commits into from Jul 29, 2022

Conversation

guyuqi
Copy link
Member

@guyuqi guyuqi commented Jul 29, 2022

Description of PR

1.Fix Hive build issues about protobuf 2.5.0 on Arm64 and
PPC64le when upgrading hadoop to 3.3.3/3.3.4,
2.Expand Java heap size.

How was this patch tested?

For code changes:

Build Hive and run smoke tests

  • Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
  • Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

…PPC64le

1.Fix Hive build issues about protobuf 2.5.0 on Arm64 and
PPC64le when upgrading hadoop to 3.3.3/3.3.4,
2.Expand Java heap size.

Change-Id: Iea3fb2bc110210b990031fb13b3ec3aeb4c83109
Signed-off-by: Yuqi Gu <yuqi.gu@arm.com>
@guyuqi
Copy link
Member Author

guyuqi commented Jul 29, 2022

Tested it on Arm64 rockylinux8:

 ./docker-hadoop.sh --create 3 \
--image bigtop/puppet:trunk-rockylinux-8 \
--memory 16g \
--repo file:///bigtop-home/output \
--disable-gpg-check --enable-local-repo \
--stack hdfs,yarn,mapreduce,hbase,hive \
--smoke-tests hive

fi
export MAVEN_OPTS="${MAVEN_OPTS} -Xmx1500m -Xms1500m"
export MAVEN_OPTS="${MAVEN_OPTS} -Xmx2500m -Xms2500m"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about removing -Xms1500m to make JVM allocate heap on demand? We can not expect much gain by allocating maximum heap from the beginning for short term task like building products. I got no OOM with current settings on my x86_64 environment.

Copy link
Member Author

@guyuqi guyuqi Jul 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It makes sense.
Removed this setting and also tested it on my Arm64 environment.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While -Xmx2500m might be still useful to allocate enough heap on machine with memory less than 5GB (because the default maximum heap of JVM is capped at half of the machine's memory IIRC), we can not practically use such a small machine for Bigtop development. I think dropping -Xmx too should be ok.

Change-Id: I59811ca32e70a8a2c8eb261e55b0e8470590b7ce
Signed-off-by: Yuqi Gu <yuqi.gu@arm.com>
Copy link
Member

@iwasakims iwasakims left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. tested on CentOS 7 aarch64 .

While I got the error I commented to BIGTOP-3760, applying the patch of #964 fixed the issue.

@iwasakims iwasakims merged commit d6510af into apache:master Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants