COD allows you to customize the attached storage worker node for an HDFS cluster while creating a database. You can define the EBS volumes for HDFS clusters. You can also view the customized attached storage worker nodes using the ‘describe-database’ and ‘list-database’ commands.   This is available starting in COD v1.23 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

Certain countries may have regulatory requirements that limit or forbid specific types of data from being sent or stored outside of the country or region where an organization operates. For this reason Cloudera has introduced new regions in which the Control Plane can run. By choosing a region other than us-west-1, you can ensure that sensitive metadata (such as information about CDP users) does not leave its region or country of origin. For more information, see CDP Control Plane regions.   This is available starting in COD v1.22 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

COD ensures high availability and fault tolerance using Multi-AZ deployments. A Multi-AZ deployment means that compute infrastructure for HBase’s master and region servers are distributed across multiple AZs ensuring that when a single availability zone has an outage, only a portion of Region Servers is impacted and clients automatically switch over to the remaining servers in the available AZs. Multi-AZ for COD is currently supported only on Amazon Web Services (AWS) environments. For more information, see Multi-AZ deployment on COD.   This is available starting in COD v1.22 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

Store File Tracking (SFT) defines a separate, plugable layer to handle storefile life cycle, and includes the FILE based built-in implementation that avoids internal file rename or move operations while managing the storefiles. This is a critical enablement to deploy HBase over S3 object store, which is known for the lack of atomic renames. COD enables this feature by default for databases deployed on AWS with S3, to mitigate the aforementioned S3 limitation that could cause critical issues for HBase. For more information, see HBase Store File Tracking.   This is available starting in COD v1.22 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

COD now supports replication for the META regions, which means clients can read the META replicas first before connecting to the primary region server. This reduces the load on the META table because the read META load is distributed across multiple replicas. COD supports configuring three META replicas which can be deployed in different RegionServers. Client needs to use the COD provided configuration to get the META calls that are distributed across these replicas. This would be useful in the case where the application has lots of clients like while accessing using spark, yarn, phoenix-spark etc.   This is available starting in COD v1.21 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

If your client applications are running on Cloudera legacy products, they usually do not have Kerberos authentication enabled. When you try to connect to any COD instance, the connection fails because the COD instances have Kerberos enabled, by default. Now, you can disable Kerberos authentication in your COD instances so that HBase or Phoenix clients can connect seamlessly. For more information, see Disabling Kerberos authentication for HBase clients.   This is available starting in COD v1.19 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

You can add table coprocessors so that HBase can run custom code on the server side against the stored data and filter local minimum or maximum value during ingestion without scanning the entire table. You can use built-in table coprocessors from the upstream HBase releases.   This feature is in Preview and available on new COD services only. For more information, see Working with custom table coprocessors.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

COD is now bundled and shipped along with the HBase version 2.4.6 when the CDP Runtime version is 7.2.14.   This is available starting in COD v1.19 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

COD supports Apache OMID transactional framework that allows Big Data applications to execute ACID transactions on top of Phoenix tables.   This is available starting in COD v1.19 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

CDP Operational Database (COD) now supports the configuration of instance storage to cache HBase data stored in block storage. This is only available on AMD instance types.   This is available starting in COD v1.18 and you do not need to upgrade to a higher version of COD to benefit from this feature.   Try out CDP Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more