summaryrefslogtreecommitdiffstats
path: root/sbin/hastd/hast.conf.5
Commit message (Collapse)AuthorAgeFilesLines
* Document IPv6 support.pjd2011-05-201-8/+22
| | | | MFC after: 3 weeks
* In preparation for IPv6 support allow to specify multiple addresses topjd2011-05-191-1/+2
| | | | | | listen on. MFC after: 3 weeks
* Increase default timeout from 5 seconds to 20 seconds. 5 seconds is definitelypjd2011-04-021-2/+2
| | | | | | | to short under heavy load and I was experiencing those timeouts in my recent tests. MFC after: 1 week
* In hast.conf we define the other node's address in 'remote' variable.pjd2011-03-211-1/+13
| | | | | | | | | | | | | | | | | | This way we know how to connect to secondary node when we are primary. The same variable is used by the secondary node - it only accepts connections from the address stored in 'remote' variable. In cluster configurations it is common that each node has its individual IP address and there is one addtional shared IP address which is assigned to primary node. It seems it is possible that if the shared IP address is from the same network as the individual IP address it might be choosen by the kernel as a source address for connection with the secondary node. Such connection will be rejected by secondary, as it doesn't come from primary node individual IP. Add 'source' variable that allows to specify source IP address we want to bind to before connecting to the secondary node. MFC after: 1 week
* Allow to compress on-the-wire data using two algorithms:pjd2011-03-061-0/+20
| | | | | | | | | | | - HOLE - it simply turns all-zero blocks into few bytes header; it is extremely fast, so it is turned on by default; it is mostly intended to speed up initial synchronization where we expect many zeros; - LZF - very fast algorithm by Marc Alexander Lehmann, which shows very decent compression ratio and has BSD license. MFC after: 2 weeks
* Allow to checksum on-the-wire data using either CRC32 or SHA256.pjd2011-03-061-1/+15
| | | | MFC after: 2 weeks
* Execute hook when connection between the nodes is established or lost.pjd2010-08-301-5/+15
| | | | | MFC after: 2 weeks Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
* Execute hook when split-brain is detected.pjd2010-08-301-0/+5
| | | | | MFC after: 2 weeks Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
* - Call hook on role change.pjd2010-08-291-1/+21
| | | | | | | - Document new event. MFC after: 2 weeks Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
* Document new 'exec' parameter.pjd2010-08-271-1/+39
| | | | | MFC after: 2 weeks Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com
* Fix typos, spelling, formatting and mdoc mistakes found by Nobuyuki whilejoel2010-08-161-1/+1
| | | | | | translating these manual pages. Minor corrections by me. Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp>
* Document 'none' value for remote.pjd2010-08-051-1/+6
| | | | | Reviewed by: dougb MFC after: 1 month
* Spelling fixes.joel2010-07-311-1/+1
|
* Actually, only the fullsync mode is implemented, not memsync mode.pjd2010-07-221-3/+5
| | | | | | Correct manual page. MFC after: 3 days
* mdoc: move remaining sections into consistent orderuqs2010-05-131-13/+13
| | | | | | | This pertains mostly to FILES, HISTORY, EXIT STATUS and AUTHORS sections. Found by: mdocml lint run Reviewed by: ru
* Fix a problem where hastd will stuck in recv(2) after sending request topjd2010-04-291-0/+7
| | | | | | | | | | secondary, which died between send(2) and recv(2). Do it by adding timeout to recv(2) for primary incoming and outgoing sockets and secondary outgoing socket. Reported by: Mikolaj Golub <to.my.trociny@gmail.com> Tested by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Please welcome HAST - Highly Avalable Storage.pjd2010-02-181-0/+267
HAST allows to transparently store data on two physically separated machines connected over the TCP/IP network. HAST works in Primary-Secondary (Master-Backup, Master-Slave) configuration, which means that only one of the cluster nodes can be active at any given time. Only Primary node is able to handle I/O requests to HAST-managed devices. Currently HAST is limited to two cluster nodes in total. HAST operates on block level - it provides disk-like devices in /dev/hast/ directory for use by file systems and/or applications. Working on block level makes it transparent for file systems and applications. There in no difference between using HAST-provided device and raw disk, partition, etc. All of them are just regular GEOM providers in FreeBSD. For more information please consult hastd(8), hastctl(8) and hast.conf(5) manual pages, as well as http://wiki.FreeBSD.org/HAST. Sponsored by: FreeBSD Foundation Sponsored by: OMCnet Internet Service GmbH Sponsored by: TransIP BV
OpenPOWER on IntegriCloud