IBM© DataPower Operations Dashboard v1.0.5.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

The DPODs Big Data Store is located on a dedicated hard drive.

From time to time there is a need to extended the amount of disk space that is allocated for the Store.

The reasons could be increase in TPS or requirement to keep history for longer time.

Increasing the amount of disk space allocated to DPODs Store involves two stages:

Increase the Data Disk and File System

Physical Server

In order to increase the data disk and file system for physical server use the servers vendor RAID management software to extend the exiting RAID Disk (LUN) or add new RAID Disk (new LUN) .

Based on the action on the previous stage (extend / add disk) follow the procedure for the OS level configuration :

Virtual appliance

There are two strategies for increasing the disk space for the DPODs Store  

Extend the existing virtual disk

Use the vSphere Client in order to edit the DPODs virtual machine

    • Stop DPOD virtual machine.
    • Press “Edit virtual machine settings”
    • Choose the 3rd hard drive (which is the data disk as described in DPODs Hardware and Software Requirements).
    • Increase the “Provisioned size” of the hard drive and press OK.
    • Wait for the increase process to finish.
    • Start DPOD virtual machine.

 

Configure the extended disk on OS level

    • Display the current size of mount point / data : df -h /data



    • Display the new disk size : fdisk -l |grep /dev/sdc



    • Create new partition for the new size :
      • fdisk /dev/sdc
      • Press p to print the partition table to identify the number of partitions.
        If this is the first disk extending there should be only sdc1. If this is the second time there should be sdc1 and sdc2.



      • Press n to create a new primary partition.
      • Press p for primary.
      • Press 2 for the partition number, depending on the output of the partition table print (if this is the second disk extending then the partition number will be 3 )
      • Press Enter two times.



      • Press t to change the system's partition ID.
      • Press 2 to select the newly creation partition.
      • Type 8e to change the Hex Code of the partition for Linux LVM.
      • Press w to write the changes to the partition table.



        the following warning is valid, the system reboot will fix the issue :
        “WARNING: Re-reading the partition table failed with error 16: Device or resource busy.The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8)”



      • Reboot the system : reboot
      • After the system is up, make sure you see the new partition : fdisk -l |grep /dev/sdc



      • stop the application using app-util.sh -> option 2 (stop all)
      • create new LVM physical volume (PV) : pvcreate /dev/sdc2
        if this is the second disk extending the device will be /dev/sdc3
      • extend the LVM volume group (VG) : vgextend vg_data /dev/sdc2
      • extend the LVM logical volume (LV) :
        lvextend -l +100%FREE /dev/vg_data/lv_data
      • identify the /data file system type (for CentOS 7.2 based appliance the type is xfs) : cat /etc/fstab |grep /data



      • resize the file system according to the file system type :
      • ext4 : resize2fs /dev/vg_data/lv_data
      • xfs : xfs_growfs /dev/vg_data/lv_data



      • Display the new  size of mount point / data : df -h /data

 

Add new virtual disk

Use the vSphere Client in order to edit the DPODs virtual machine

    • Stop DPOD virtual machine.
    • Press “Edit virtual machine settings”
    • Choose “add” -> “hard drive”
      make sure you configure the new hard drive as “Thick Provision Eager Zeroed”



    • Wait for the increase process to finish.
    • Wait for the increase process to finish.
    • Start DPOD virtual machine.

Configure the new disk on OS level


    • Display the current size of mount point / data : df -h /data


    • Display the new disk size : fdisk -l |grep /dev/sdd



  • Create new partition for the new size :
    • fdisk /dev/sdd
    • Press p to print the partition table and make sure there are no partitions.



    • Press n to create a new primary partition.
    • Press p for primary.
    • Press 1 for the partition number
    • Press Enter two times.



    • Press t to change the system's partition ID.
    • Type 8e to change the Hex Code of the partition for Linux LVM.
    • Press w to write the changes to the partition table.



    • Reboot the system : reboot
    • After the system is up, make sure you see the new partition : fdisk -l |grep /dev/sdd



    • stop the application using app-util.sh -> option 2 (stop all)
    • create new LVM physical volume (PV) : pvcreate /dev/sdd1
    • extend the LVM volume group (VG) : vgextend vg_data /dev/sdd1
    • extend the LVM logical volume (LV) :
      lvextend -l +100%FREE /dev/vg_data/lv_data
    • identify the /data file system type (for CentOS 7.2 based appliance the type is xfs) : cat /etc/fstab |grep /data



    • resize the file system according to the file system type :
    • ext4 : resize2fs /dev/vg_data/lv_data
    • xfs : xfs_growfs /dev/vg_data/lv_data



    • Display the new  size of mount point / data : df -h /data

 

Update the Store Configuration File

Update the Store configuration file :

  • please run the following script:

     /app/scripts/update_store_allocation.sh  

    The script is available on DPOD v1.0.4.0 and above. If you are using earlier version please contact DPOD support and the script will be provided.

  • start the application using app-util.sh -> option 1 (start all)



  • No labels