summaryrefslogtreecommitdiffstats
path: root/sbin/hastd
Commit message (Collapse)AuthorAgeFilesLines
* Default connection timeout is way too long. To make it shorter we have topjd2010-04-291-3/+75
| | | | | | | | | make socket non-blocking, connect() and if we get EINPROGRESS, we have to wait using select(). Very complex, but I know no other way to define connection timeout for a given socket. Reported by: hiroshi@soupacific.com MFC after: 3 days
* - Check if the worker process was killed by signal and restart it.pjd2010-04-291-18/+26
| | | | | | | - Improve logging. Pointed out by: Garrett Cooper <yanefbsd@gmail.com> MFC after: 3 days
* Fix a problem where hastd will stuck in recv(2) after sending request topjd2010-04-2910-3/+87
| | | | | | | | | | 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
* Restart worker thread only if the problem was temporary.pjd2010-04-281-3/+9
| | | | | | In case of persistent problem we don't want to loop forever. MFC after: 3 days
* Mark temporary issues as such.pjd2010-04-281-2/+2
| | | | MFC after: 3 days
* Use WEXITSTATUS() to obtain real exit code.pjd2010-04-281-2/+3
| | | | MFC after: 3 days
* Don't assume that "resource" property is in metadata.pjd2010-04-281-1/+1
| | | | | Reported by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Fix compilation with WITHOUT_CRYPT or WITHOUT_OPENSSL options.pjd2010-04-222-3/+15
| | | | | Reported by: Andrei V. Lavreniyuk <andy.lavr@reactor-xg.kiev.ua> MFC after: 3 days
* Fix log size calculation which caused message truncation.pjd2010-04-161-1/+1
| | | | | Submitted by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Fix control socket leak when worker process exits.pjd2010-04-161-0/+1
| | | | | Submitted by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Increase ggate queue size to maximum value.pjd2010-04-151-1/+1
| | | | | | | HAST was not able to stand heavy random load. Reported by: Hiroyuki Yamagami MFC after: 3 days
* Don't hold connection lock when doing reconnects as it makes I/Os wait forpjd2010-03-271-26/+50
| | | | | | connection timeouts. Reported by: Kevin Day <toasty@dragondata.com>
* Remove redundant WARNS?=6 overrides and inherit the WARNS setting fromuqs2010-03-021-1/+0
| | | | | | | | the toplevel directory. This does not change any WARNS level and survives a make universe. Approved by: ed (co-mentor)
* Fixed static linkage.ru2010-02-261-2/+3
|
* Changing proto_socketpair.c compilation and linking order revealedpjd2010-02-211-1/+4
| | | | | a problem - we should simply ignore proto_server() if address doesn't start with socketpair://, and not abort.
* Please welcome HAST - Highly Avalable Storage.pjd2010-02-1838-0/+10308
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