| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
- Improve logging.
Pointed out by: Garrett Cooper <yanefbsd@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
In case of persistent problem we don't want to loop forever.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
| |
Reported by: Andrei V. Lavreniyuk <andy.lavr@reactor-xg.kiev.ua>
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
| |
HAST was not able to stand heavy random load.
Reported by: Hiroyuki Yamagami
MFC after: 3 days
|
|
|
|
|
|
| |
connection timeouts.
Reported by: Kevin Day <toasty@dragondata.com>
|
|
|
|
|
|
|
|
| |
the toplevel directory.
This does not change any WARNS level and survives a make universe.
Approved by: ed (co-mentor)
|
| |
|
|
|
|
|
| |
a problem - we should simply ignore proto_server() if address
doesn't start with socketpair://, and not abort.
|
|
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
|