For hardware requirements, see Single-Node Deployments.
Note: Do not run other software on a server where you intend to install and deploy Tamr.
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 exist to manage specific applications.
Tamr recommends that you create a local functional system account, such as
tamr, to use for all Tamr deployment and administration tasks. Specifics follow. Use of an externally-managed standard user account is not recommended.
This documentation refers to the functional system account for the administration of Tamr and its dependencies as the “functional user”.
Note: 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
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), and do not require
Important: Never use the
root user to install or upgrade Tamr, or to start or stop Tamr services or dependencies.
Configure the following
ulimit resource limits for the
tamr functional user.
ulimit resource limits
- Create a new file,
99-tamr.confin the directory
/etc/security/limits.d. Do not edit the file
- Add the 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
Log out and then log in again as the
tamrfunctional user to set the new values.
Verify the current values:
- The maximum number of open files (
nofile) is 1000000. To confirm the current value, run
- The maximum number of user processes (
nproc) is 104381. To confirm the current value, run
For more information about
ulimit resource limits, see:
You can change the maximum number of memory map areas a process may have, specified with
vm.max_map_count. The maximum number of memory map areas is 262144.
- Edit the file
/etc/sysctl.confand add a line at the end containing:
sudo sysctl -pto use the newly set value
sysctl vm.max_map_countto confirm the current value
- You can access the user interface for Tamr and Tamr APIs over a single port for inbound web access. The default HTTP port Tamr uses is
- Tamr and its dependent services use other ports, but these typically do not need to be exposed for inbound access.
- Optionally, we recommend to make the monitoring port accessible for inbound web traffic. The default port number is
31101. For more information, see Monitoring.
The Tamr software bundle is
unify.zip. In addition to the Tamr software package, the software bundle includes the following dependencies:
Tamr requires PostgreSQL v12. Since Postgres 10, minor releases of Postgres contain only bug and security fixes. These minor releases are fully compatible with each other. We recommend installing or upgrading to the latest minor version of Postgres 12. See Installing Postgres and Upgrading Postgres.
|Windows 7/8.1||Supported||Supported (recommended)||Supported (recommended)|
|Windows 10||Supported||Not Tested||Not Tested|
|Linux OS||N/A||Not Supported||Not Supported|
Updated 17 days ago