More on Vertica Database Tutorials

(We marked visited pages blue)
  • How to measure the Size of your HP Vertica Database Catalog
  • How to Change HP Vertica Cluster Spread messaging Type
  • How to Change HP Vertica Data Locations and Drop Old Storage Location
  • Vertica Database Script to monitor Data Load Streams
  • HP Vertica 8 "Frontloader" Released
  • Learn how to manage your Vertica Data load Streams
  • How to remove Storage Location in HP Vertica database
  • Fix for Vertica ERROR 2035 COPY Invalid integer format
  • Easy procedure to clone a Vertica Database User
  • How to Disable Vertica Data Collector
  • Vertica database System Tables Lock Down
  • How to Create Vertica Schema on the Fly
  • HP Vertica Backup Fix for Error RSYNC error in rsync protocol data stream (code 12)
  • Vertica Management Console Upgrade 7.2.1 to 7.2.2
  • Fix of Error ERROR AHM must lag behind the create epoch of unrefreshed projection
  • Vertica Dimension Wars and Initial database tunning
  • Welcome Inheritence
  • Dropping Sequences headache
  • Quick and Dirty HP Vertica Schema Clone
  • How to Recover a lost node in Vertica database
  • What about that Vertica WRITE ONCE stuff !
  • Solution for error vsql FATAL 5273 Unsupported frontend protocol 3.5 server supports 3.0 to 3.4
  • How Partition Pruning work in Vertica
  • Transform data during load in Vertica - use variable with COPY
  • How to Skip a column when loading data in Vertica
  • How to Export the Catalog in Vertica
  • How to Skip data when loading data in Vertica Database
  • HP Vertica database validation Scripts
  • Vertica JDBC connection string
  • How to create a Linked Server from SQL Server to HP Vertica
  • Live Documentation in Vertica using comment on
  • Vertica Stock Schema Example Database
  • How to Generate a Stock Schema Example for Vertica Database
  • Vertica Profile Management
  • Fix for Vertica ERROR Join did not fit in memory
  • What are the User Privileges in Vertica database
  • Privileges required for Table operations in HP Vertica
  • How to Manage users accounts in HP Vertica Database
  • How to change the owner of a table in Vertica
  • Vertica Tiered Storage Policies
  • Setting the purge policy in Vertica
  • Managing the Vertica database parameters
  • Migrate entire Schema in Vertica
  • How to Manage and Work with Data Collector in Vertica
  • Create new storage location in HP Vertica database.
  • Understanding Vertica Storage Mechanism
  • How to get the raw size of your data in HP Vertica
  • Working with Merge in Vertica
  • How to work External Tables in Vertica
  • Vertica Superuser(Dbadmin)
  • How to optimize Vertica Merge statement performance
  • How to ignore or avoid a projection to be used in Vertica
  • Uninstall and cleanup an old HP Vertica installation
  • How to Import data from MySQL into Vertica with one single line of code
  • Export data into cvs format from Vertica using the vsql Meta-Commands
  • Working with Vertica TRUST Authentication method
  • Migrate SQL Server to HP Vertica in a single step
  • How to fix HP Vertica Installation FAILED with errors
  • HP Vertica installation error FAIL (S0310) fix
  • HP Vertica installation error FAIL (S0300) fix
  • HP Vertica installation error FAIL (S0020) fix
  • Tutoriais Vertica
  • Script to Extract Roles atribution Definition in Vertica
  • Working with HP Vertica Flex Tables
  • Vertica SHOW command
  • Vertica Export & Import a single table
  • How to upgrade the license_key in Vertica database
  • How to Monitor Mergeout in Vertica ?
  • HP Vertica Lock Types and Conflicts Management
  • HP Vertica compute_flextable_keys() function
  • HP Vertica build_flextable_view () function
  • HP Vertica Backup and Recover with examples
  • How to create a Full HP Vertica database backup
  • Find used resources plus the used pool details of a single Vertica statement
  • How to recover a Vertica node from a failed start
  • Vsql command line options in Vertica
  • Vertica Vsql command line examples
  • Vertica troubleshooting teqniques
  • Vertica SHOW command
  • Vertica Segmentation
  • Vertica Management Console Tutorials
  • Vertica Drop Schema command
  • Vertica Database Projections Types
  • Vertica database Export and Import a single table
  • Vertica Database Create User command
  • Vertica Create Schema command
  • Vertica "Copy From" command
  • Vertica Backup and Recover step by step
  • Vertica Alter Schema
  • Vertica admintools options
  • Replication Concepts used in Vertica Database
  • Export and Import a Table in Vertica
  • Drop User in Vertica
  • How delete process works in Vertica database
  • Data Type we can use in Vertica
  • Create Profile in Vertica Database
  • Changing Currency Format in Vertica
  • How to change Vertica Cluster IP address step by step
  • Alter User in Vertica
  • Vertica Projection structure
  • Vertica installation on Linux step by step
  • Vertica hybrid storage model
  • Vertica database Storage Concepts
  • Vertica database Logical and physical schema concepts
  • Vertica database K-safety
  • What are the Data compression and encoding types in Vertica
  • Get your HP Vertica Administrator certification
  • Vertical Cluster Prerequisite Installation
  • Vertica Pos-Installation Tasks
  • Vertica and PHP connector
  • Vertica currency format change
  • Vertica client install on Windows
  • What is HP Vertica Architecture Type Like
  • Upgrade HP Vertica database from 6.1 to 7.0
  • How to Uninstall Vertica Database
  • How to uninstall Vertica database
  • How to start and stop Vertica from admintools comand line
  • How to setup restart policy of our Vertica database using the admintools command line
  • How to recover a Vertica node from a failed start
  • How to re-balance data on Vertica using the admintools command line
  • How to measure disk IO speed in Vertica
  • How to list all Vertica database nodes using the admintools command line
  • Installing Vertica ODBC on Windows
  • Install .NET provider for Vertica
  • How to install a HP Vertica Database Cluster
  • How to find installed packages on Vertica server using the admintools command line
  • How to extract day from timestamp in Vertica
  • How to Export/Import object DDL and data in Vertica
  • How to export data from Vertica to MS Excel
  • What is different in Vertica
  • How to connect to the Vertica database using the admintools command line
  • Change Vertica cluster ip address
  • How to change the LOCALE on Vertica database
  • Change Language in Vertica
  • How to Alter DateStyle in Vertica
  • Vertica Database Replication Concepts
  • What is the Execution model of a HP Vertica query
  • 9 - HP Vertica Database Intro Series
  • 8 - HP Vertica Database Intro Series
  • 7 - HP Vertica Database Intro Series
  • 5 - HP Vertica Database Intro Series
  • HP Vertica Database Key Components
  • 3 - HP Vertica Database Intro Series
  • 2 - HP Vertica Database Intro Series
  • 1 - HP Vertica Database Intro Series
  • HP Vertica installation error FAIL (S0150) fix

    This is a short fix for the error FAIL(S0150) that comes up during the HP Vertica Installation.

    FAIL (S0150):These disks do not have 'deadline' or 'noop' IO scheduling: '/dev/sda1'
            ('sda') = 'cfq'
    HP Vertica requires that I/O Scheduling be set to deadline or noop. What are the IO scheduling types : Input/output (I/O) scheduling is the method that computer operating systems use to decide which order block I/O operations will be submitted to storage volumes. I/O schedulers can have many purposes depending on the goal of the I/O scheduler. Some common ones are:
    • To minimize time wasted by hard disk seeks
    • To prioritize a certain processes' I/O requests
    • To give a share of the disk bandwidth to each running process
    • To guarantee that certain requests will be issued before a particular deadline
    Types of scheduling
    • Random scheduling
    • First In, First Out (FIFO), also known as First Come First Served (FCFS)
    • Last In, First Out (LIFO)
    • Shortest seek first, also known as Shortest Seek / Service Time First (SSTF)
    • Elevator algorithm, also known as SCAN (including its variants, C-SCAN, LOOK, and C-LOOK)
    • N-Step-SCAN SCAN of N records at a time
    • FSCAN, N-Step-SCAN where N equals queue size at start of the SCAN cycle
    • Completely Fair Queuing (CFQ) on Linux
    • Anticipatory scheduling
    • Noop scheduler
    • Deadline scheduler
    We are not going to explain all of them, we will only talk about the ones that HP Vertica recommend using and why. There two are deadline and noop. deadline -The Deadline scheduler gives priority to read requests over write requests. It also imposes a deadline on all requests. After reaching the deadline, such requests gain priority over all other requests. This scheduling methods helps prevent processes from becoming starved for I/O access. noop -The NOOP scheduler inserts all incoming I/O requests into a simple FIFO queue and implements request merging. This scheduler is useful when it has been determined that the host should not attempt to re-order requests based on the sector numbers contained therein. In other words, the scheduler assumes that the host is definitively unaware of how to productively re-order requests. This scheduler is best used on solid state drives (SSDs). Since SSDs do not have a physical read head, no performance penalty exists when accessing non-adjacent sectors. Let's go an see how we can fix this erros HP Vertica requires that IO scheduler be set to deadline or noop Viewing the contents of the /sys/block//queue/scheduler file to see you actual schedule definition. Where
    [root@primary tmp]# cd  /sys/block
    [root@primary block]# ll
    total 0
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 dm-0 - ../devices/virtual/block/dm-0
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 dm-1 - ../devices/virtual/block/dm-1
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop0 - ../devices/virtual/block/loop0
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop1 - ../devices/virtual/block/loop1
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop2 - ../devices/virtual/block/loop2
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop3 - ../devices/virtual/block/loop3
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop4 - ../devices/virtual/block/loop4
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop5 - ../devices/virtual/block/loop5
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop6 - ../devices/virtual/block/loop6
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 loop7 - ../devices/virtual/block/loop7
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram0 - ../devices/virtual/block/ram0
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram1 - ../devices/virtual/block/ram1
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram10 - ../devices/virtual/block/ram10
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram11 - ../devices/virtual/block/ram11
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram12 - ../devices/virtual/block/ram12
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram13 - ../devices/virtual/block/ram13
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram14 - ../devices/virtual/block/ram14
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram15 - ../devices/virtual/block/ram15
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram2 - ../devices/virtual/block/ram2
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram3 - ../devices/virtual/block/ram3
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram4 - ../devices/virtual/block/ram4
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram5 - ../devices/virtual/block/ram5
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram6 - ../devices/virtual/block/ram6
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram7 - ../devices/virtual/block/ram7
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram8 - ../devices/virtual/block/ram8
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 ram9 - ../devices/virtual/block/ram9
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 sda - ../devices/pci0000:00/0000:00:0d.0/host2/target2:0:0/2:0:0:0/block/sda
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 sdb - ../devices/pci0000:00/0000:00:0d.0/host3/target3:0:0/3:0:0:0/block/sdb
    lrwxrwxrwx 1 root root 0 Feb 24 14:21 sr0 - ../devices/pci0000:00/0000:00:01.1/host1/target1:0:0/1:0:0:0/block/sr0
    In my case the devices that are going to be used for the HP Vertica install is sda. To it's definition :
    [root@primary block]# cat /sys/block/sda/queue/scheduler
    noop anticipatory deadline [cfq]
    To change the scheduler, write the name of the scheduler you want the device to use to its scheduler file. You must have root privileges to write to this file. For example, to set the sda drive to use the deadline scheduler, run the following command as root:
    [root@primary block]# echo deadline  /sys/block/sda/queue/scheduler
    [root@primary block]# cat /sys/block/sda/queue/scheduler
    noop anticipatory [deadline] cfq


    Leave a comment or a question in the comment area bellow if you fell like


    Be a sport and

    Search

    Loading... Please wait

    Subscribe to our Newsletter

    Be a sport and

    x