Information Cartes HBA
[root@rltesa2 ]# cat /sys/bus/pci/drivers/qla2xxx/0000:24:00.0/host1/fc_host:host1/port_name
0x2100001b3294031f
[root@rltesa2 ]# cat /sys/bus/pci/drivers/qla2xxx/0000:24:00.1/host2/fc_host:host2/port_name
0x2101001b32b4031f
Mise en place du multipath LINUX
Le multipath est le mécanisme permettant d'accéder via deux chemins différents aux disques de la baie. Il est disponible sous la forme d'un service pré-installé dans RHEL 5 que nous le configurerons en « round robin ». Par ailleurs il est nécessaire d'exclure les disques internes du fonctionnement du multipath en ajoutant les lignes suivantes dans le fichier « /etc/multipath.conf » :
blacklist {
vendor "IBM-ESXS"
product "MBC2073RC"
}
Démarrage et configuration du service multipath :
service multipathd start
chkconfig --level 345 multipathd on
Vérification du bon fonctionnement du multipath
[root@rldeva1 tomcat]# multipath -ll
mpath2 (360060e800546fd00000046fd00000625) dm-39 HITACHI,OPEN-V
[size=150G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=2][active]
\_ 1:0:0:0 sdc 8:32 [active][ready]
\_ 2:0:0:0 sdd 8:48 [active][ready]
[root@rldeva1 tomcat]#
jeudi 16 juin 2011
Linux - Version Système
Version de l'OS
cat /proc/version
uname -r
uname -a
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
cat /proc/version
uname -r
uname -a
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Linux - Etendre un PV (LUN SAN) sans reboot
1 - démonter tous les FS
2 - désactiver le VG
vgchange -a n vol01
3 - Etendre la partition
via fdisk supprimer la partition et la recréer avec la nouvelle taille
Attention mettre type 8E
4 - partprobe pour la prise en compte au niveau du système
5 - pvresize du disque (LVM)
6 - contrôler la nouvelle taille PV + VG
7 - Réactiver le VG
vgchange -a y vol01
8 - Remonter tous les FS
2 - désactiver le VG
vgchange -a n vol01
3 - Etendre la partition
via fdisk supprimer la partition et la recréer avec la nouvelle taille
Attention mettre type 8E
4 - partprobe pour la prise en compte au niveau du système
5 - pvresize du disque (LVM)
6 - contrôler la nouvelle taille PV + VG
7 - Réactiver le VG
vgchange -a y vol01
8 - Remonter tous les FS
mercredi 15 juin 2011
Modifier les partitions LVM
parted /dev/sdc
GNU Parted 1.8.1
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) help
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] prints general help, or help on COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [free|NUMBER|all] display the partition table, a partition, or all devices
quit exit program
rescue START END rescue a lost partition near START and END
resize NUMBER START END resize partition NUMBER and its file system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition NUMBER
unit UNIT set the default unit to UNIT
version displays the current version of GNU Parted and copyright information
GNU Parted 1.8.1
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) help
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] prints general help, or help on COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on partititon NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [free|NUMBER|all] display the partition table, a partition, or all devices
quit exit program
rescue START END rescue a lost partition near START and END
resize NUMBER START END resize partition NUMBER and its file system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition NUMBER
unit UNIT set the default unit to UNIT
version displays the current version of GNU Parted and copyright information
mardi 14 juin 2011
Increase Primary Partition On LVM2
pvresize --setphysicalvolumesize 30G /dev/sdc1
pvresize --setphysicalvolumesize 30G /dev/sdc1
WARNING: /dev/sdc1: Overriding real size. You could lose data.
Physical volume "/dev/sdc1" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
pvscan
PV /dev/sdc1 VG VGappli lvm2 [29.97 GB / 11.88 GB free]
PV /dev/sdb1 VG VGswap lvm2 [3.97 GB / 0 free]
PV /dev/sda2 VG VGsystem lvm2 [11.47 GB / 0 free]
Total: 3 [45.41 GB] / in use: 3 [45.41 GB] / in no VG: 0 [0 ]
pvresize --setphysicalvolumesize 30G /dev/sdc1
WARNING: /dev/sdc1: Overriding real size. You could lose data.
Physical volume "/dev/sdc1" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
pvscan
PV /dev/sdc1 VG VGappli lvm2 [29.97 GB / 11.88 GB free]
PV /dev/sdb1 VG VGswap lvm2 [3.97 GB / 0 free]
PV /dev/sda2 VG VGsystem lvm2 [11.47 GB / 0 free]
Total: 3 [45.41 GB] / in use: 3 [45.41 GB] / in no VG: 0 [0 ]
jeudi 9 juin 2011
JDBC Specification
JDBC Connection Pool
* Added by helenlong, last edited by grisdal on Feb 23, 2009 (view change)
Comment:
JDBC Connection Pool
The JDBC Connection Pool page provides information about the connection pool and plots change over time. Connection pool data will only be available if the JDBC resource is deployed and enabled on the server instance or cluster. Because most of the graphs plot change over time, a very lightly loaded system may show little activity. The JDBC connection pool graphs are very similar to the connector connection pool graphs and plot similar data (see Connector Connection Pool).
The following data is displayed.
* Maximum Pool Size. Maximum number of connections that can be created to satisfy client requests.
* Leak Reclaim Enabled. If enabled, connection will be reusable (put back into the pool) after connection leak timeout occurs.
* Datasource Classname. The vendor-specific class name that implements the DataSource and/or XADataSource APIs. This class is in the JDBC driver.
Connection Utilization
* # of Connections. (Graph) Current status of the connections in this pool.
Data plotted in this graph:
* Free. Number of connections in the pool available for incoming requests.
* In Use. Number of connections in the pool currently being used. When the number of in use connections goes up, the number of free connections will drop.
* In Queue. Number of requests in the queue waiting for available connections.
* Total Created. Total number of connections ever created for this pool since server startup. For example, if the number in use shows 3, but the total created shows 10, there was a load at some point that spiked to that level.
The Connection Utilization graph works in sync with the Wait Time graph described below. When requests start queueing up and wait times start increasing, that is a sign the pool is under stress. Consider changing the maximum pool size for this connection pool or performing other tuning, keeping in mind that increasing the maximum pool size might decrease the wait time, but it will also increase load on your database.
Wait Time
* Duration (ms). (Graph) How long users of this pool have been waiting for service in milliseconds. Wait time shows how overloaded the pool might be (if wait time is excessive.)
Data plotted in this graph:
* Wait Time. How long the last request to the pool waited to get a connection.
* Average Wait Time. Average wait time for all requests since the server started.
* Max Wait Time. Longest time a request waited for a connection since the server started. Similar to Total Created above.
Pool Utilization Rate
* Connections Per Second. (Graph) Plots both the reuse and recycle of connections.
Data plotted in this graph:
* Reused. Rate at which connections are being acquired (reused) instead of created.
* Recycled. Rate at which the pool must recycle connections, destroying connections and recreating them.
Pool Life Cycle
* Connections Per Interval. (Graph) Tracks connection creation and destruction over time for insight into leaks. Pool lifecycle indicates how often connections are being destroyed and recreated. Too often indicates poor pool utilization. If connections are leaking, that may also be revealed in this graph if the create/destroy numbers do not match up over time.
Data plotted in this graph:
* Created. Number of connections created during this particular interval since the last refresh of the view.
* Destroyed. Number of connections destroyed during this particular interval since the last refresh of the view.
* Potential Leaks. Number of connections created but not getting destroyed. Could indicate a leak. This should be zero. If you start seeing a value, further investigation is warranted.
See Also
Monitoring Components and Services
JDBC Resources
* Added by helenlong, last edited by grisdal on Feb 23, 2009 (view change)
Comment:
JDBC Connection Pool
The JDBC Connection Pool page provides information about the connection pool and plots change over time. Connection pool data will only be available if the JDBC resource is deployed and enabled on the server instance or cluster. Because most of the graphs plot change over time, a very lightly loaded system may show little activity. The JDBC connection pool graphs are very similar to the connector connection pool graphs and plot similar data (see Connector Connection Pool).
The following data is displayed.
* Maximum Pool Size. Maximum number of connections that can be created to satisfy client requests.
* Leak Reclaim Enabled. If enabled, connection will be reusable (put back into the pool) after connection leak timeout occurs.
* Datasource Classname. The vendor-specific class name that implements the DataSource and/or XADataSource APIs. This class is in the JDBC driver.
Connection Utilization
* # of Connections. (Graph) Current status of the connections in this pool.
Data plotted in this graph:
* Free. Number of connections in the pool available for incoming requests.
* In Use. Number of connections in the pool currently being used. When the number of in use connections goes up, the number of free connections will drop.
* In Queue. Number of requests in the queue waiting for available connections.
* Total Created. Total number of connections ever created for this pool since server startup. For example, if the number in use shows 3, but the total created shows 10, there was a load at some point that spiked to that level.
The Connection Utilization graph works in sync with the Wait Time graph described below. When requests start queueing up and wait times start increasing, that is a sign the pool is under stress. Consider changing the maximum pool size for this connection pool or performing other tuning, keeping in mind that increasing the maximum pool size might decrease the wait time, but it will also increase load on your database.
Wait Time
* Duration (ms). (Graph) How long users of this pool have been waiting for service in milliseconds. Wait time shows how overloaded the pool might be (if wait time is excessive.)
Data plotted in this graph:
* Wait Time. How long the last request to the pool waited to get a connection.
* Average Wait Time. Average wait time for all requests since the server started.
* Max Wait Time. Longest time a request waited for a connection since the server started. Similar to Total Created above.
Pool Utilization Rate
* Connections Per Second. (Graph) Plots both the reuse and recycle of connections.
Data plotted in this graph:
* Reused. Rate at which connections are being acquired (reused) instead of created.
* Recycled. Rate at which the pool must recycle connections, destroying connections and recreating them.
Pool Life Cycle
* Connections Per Interval. (Graph) Tracks connection creation and destruction over time for insight into leaks. Pool lifecycle indicates how often connections are being destroyed and recreated. Too often indicates poor pool utilization. If connections are leaking, that may also be revealed in this graph if the create/destroy numbers do not match up over time.
Data plotted in this graph:
* Created. Number of connections created during this particular interval since the last refresh of the view.
* Destroyed. Number of connections destroyed during this particular interval since the last refresh of the view.
* Potential Leaks. Number of connections created but not getting destroyed. Could indicate a leak. This should be zero. If you start seeing a value, further investigation is warranted.
See Also
Monitoring Components and Services
JDBC Resources
lundi 6 juin 2011
Inscription à :
Articles (Atom)