This topic describes the hardware, software, and user requirements for installing Tamr Core, and lists supported browser versions.
For hardware requirements, see Single-Node Deployments.
Important: Do not run other software on a server where you intend to install and deploy Tamr Core.
Tamr Core can be deployed on the following operating systems:
Operating system users are identified by either standard user accounts, tied to individual people at your organization, or functional system accounts, which are privileged differently and are used to manage specific applications.
Tamr recommends that you create a local functional system account, such as
tamr, to use for all Tamr Core deployment and administration tasks, as described below. Tamr recommends against using an externally-managed standard user account.
This documentation refers to the functional system account for the administration of Tamr Core and its dependencies as the “functional user”.
Important: The username for the functional account must not contain the backslash (\) character. If the account you use to manage Tamr includes this character, Spark jobs fail to run.
To create an operating system functional user, such as
tamr, see the following resources:
PostgreSQL install or upgrade must be performed by a user with
All other install or upgrade steps must be performed as the functional user (for example,
tamr). The user performing these steps does not require
Important: Never use the
rootuser to install or upgrade Tamr Core, or to start or stop Tamr Core services or dependencies.
Configure the following
ulimit resource limits for the
tamr functional user.
ulimit resource limits:
- Create a new
99-tamr.conffile in the
/etc/security/limits.ddirectory. Do not edit the file
- Add configuration to this file as shown in the following example.
# /etc/security/limits.d/99-tamr.conf * soft nofile 1000000 * hard nofile 1000000 * soft nproc 104381 * hard nproc 104381
- Sign out and then sign in again as the
tamrfunctional user to set the new values.
- Verify the current values:
- Maximum number of open files (
nofile) is 1000000. To confirm the current value, run
- Maximum number of user processes (
nproc) is 104381. To confirm the current value, run
- Maximum number of open files (
For more information about
ulimit resource limits, see the following:
You can change the maximum number of memory map areas a process may have, specified with
vm.max_map_count. The minimum number of memory map areas is 262144.
- Edit the
/etc/sysctl.conffile; add a line at the end containing:
<value>is the maximum number of memory map areas for a process.
sudo sysctl -pto use the newly set value.
If you receive a "Could not parse vm.max_map_count value" error message, follow the instructions below to add permissions to the tamr functional user.
sysctl vm.max_map_countto confirm the current value.
To add permissions to the tamr functional user:
- Add the following line to the tamr functional user’s .bash_profile or .bashrc:
- Log in again as the tamr functional user to put the change into effect.
You can access the Tamr Core user interface and APIs over a single port for inbound web access. The default HTTP port Tamr Core uses is
Tamr Core and its dependent services use other ports, but typically these ports do not need to be exposed for inbound access.
Optionally, Tamr recommends that you expose the monitoring port for inbound web traffic. The default port number is
31101. For more information, see Monitoring.
Tamr Core requires PostgreSQL v12. To ensure your installation has the latest bug and security fixes, install or upgrade to the latest minor version of PostgreSQL v12 . See Installing Postgres and Upgrading Postgres.
Updated about 1 month ago