You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
yacy_search_server/htroot/IndexControl_p.html

103 lines
3.8 KiB

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
<title>YaCy '#[clientname]#': Index Control</title>
#[metas]#
</head>
<body marginheight="0" marginwidth="0" leftmargin="0" topmargin="0">
#[header]#
<br><br>
<h2>Index Administration</h2>
<form action="IndexControl_p.html" method="post" enctype="multipart/form-data">
<p>
The local index currently consists of (at least) #[wcount]# reverse word indexes and #[ucount]# URL references<br>
*) Asynchronous queuing of crawl job URLs (stackCrawl) various checks like the blacklist check or the robots.txt disallow check are now done by a separate thread to unburden the indexer thread(s) TODO: maybe we have to introduce a threadpool here if it turn out that this single thread is a bottleneck because of the time consuming robots.txt downloads *) improved index transfer The index selection and transmission is done in parallel now to improve index transfer performance. TODO: maybe we could speed up performance by unsing multiple transmission threads in parallel instead of only a single one. *) gzip encoded post requests it is now configureable if a gzip encoded post request should be send on intex transfer/distribution *) storage Peer (very experimentell and not optimized yet) Now it's possible to send the result of the yacy indexer thread to a remote peer istead of storing the indexed words locally. This could be done by setting the property "storagePeerHash" in the yacy config file - Please note that if the index transfer fails, the index ist stored locally. - TODO: currently this index transfer is done by the indexer thread. To seedup the indexer a) this transmission should be done in parallel and b) multiple chunks should be bundled and transfered together *) general performance improvements - better memory cleanup after http request processing has finished - replacing some string concatenations with stringBuffers - replacing BufferedInputStreams with serverByteBuffer - replacing vectors with arraylists wherever possible - replacing hashtables with hashmaps wherever possible This was done because function calls to verctor or hashtable functions take 3 time longer than calls to functions of arraylists or hashmaps. TODO: we should take a look on the class serverObject which is inherited from hashmap Do we realy need a synchronization for this class? TODO: replace arraylists with linkedLists if random access to the list elements is not needed *) Robots Parser supports if-modified-since downloads now If the downloaded robots.txt file is older than 7 days the robots parser tries to download the robots.txt with the if-modified-since header to avoid unnecessary downloads if the file was not changed. Additionally the ETag header is used to detect changes. *) Crawler: better handling of unsupported mimeTypes + FileExtension *) Bugfix: plasmaWordIndexEntity was not closed correctly in - query.java - plasmaswitchboard.java *) function minimizeUrlDB added to yacy.java this function tests the current urlHashDB for unused urls ATTENTION: please don't use this function at the moment because it causes the wordIndexDB to flush all words into the word directory! git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@853 6c8d7289-2bf4-0310-a012-ef5d649a1542
19 years ago
To transfer the whole index to an other peer, click <a href="IndexTransfer_p.html">here</a>.<br>
<table border="0" cellpadding="5" cellspacing="0">
<tr valign="top" class="TableCellDark">
<td width="70">Word</td>
<td><input type="text" name="keystring" value="#[keystring]#" size="40" maxlength="80"></td>
<td width="250"><input type="submit" name="keystringsearch" value="Show URL Entries for Word"></td>
</tr>
<tr valign="top" class="TableCellLight">
<td>Word-Hash:</td>
<td><input type="text" name="keyhash" value="#[keyhash]#" size="16" maxlength="12">
<input type="submit" name="keyhashsimilar" value="Generate List"></td>
<td><input type="submit" name="keyhashsearch" value="Show URL Entries for Word-Hash">
</td>
</tr>
<tr valign="top" class="TableCellLight">
<td></td><td></td>
<td><input type="submit" name="keyhashtransfer" value="Transfer to other peer">
<select name="hostHash">
#{hosts}#
<option value="#[hosthash]#">#[hostname]#</option>
#{/hosts}#
</select>
</td>
</tr>
</table></p>
<p><table border="0" cellpadding="5" cellspacing="0">
<tr valign="top" class="TableCellDark">
<td width="70">URL</td>
<td><input type="text" name="urlstring" value="#[urlstring]#" size="40" maxlength="250"></td>
<td width="250"><input type="submit" name="urlstringsearch" value="Show Details for URL"></td>
</tr>
<tr valign="top" class="TableCellLight">
<td>URL-Hash:</td>
<td><input type="text" name="urlhash" value="#[urlhash]#" size="16" maxlength="12">
<input type="submit" name="urlhashsimilar" value="Generate List"></td>
<td><input type="submit" name="urlhashsearch" value="Show Details for URL-Hash">
</td>
</tr>
</table></p>
<p>
DHT Transmission control:<br>
The transmission is necessary for the functionality of global search on other peers.
If you switch off distribution or receipt of RWIs you will be banned from global search.
<table border="0" cellpadding="5" cellspacing="0">
<tr valign="top" class="TableCellDark">
<td width="100">Index&nbsp;Distribution:</td>
<td><input type="checkbox" name="indexDistribute" align="top" #[indexDistributeChecked]#></td>
<td></td>
<td>This enables automated, DHT-ruled Index Transmission to other peers.
</td>
</tr>
<tr valign="top" class="TableCellDark">
<td width="100"></td>
<td>&nbsp;&nbsp;</td>
<td><input type="checkbox" name="indexDistributeWhileCrawling" align="top" #[indexDistributeWhileCrawling]#></td>
<td>If checked, DHT-Transmission is enabled even during crawling.</td>
</tr>
<tr valign="top" class="TableCellDark">
<td width="100">Index Receive:</td>
<td><input type="checkbox" name="indexReceive" align="top" #[indexReceiveChecked]#></td>
<td></td>
<td>Accept remote Index Transmissions. This works only if you are a senior peer.
The DHT-rules do not work without this function.</td>
</tr>
<tr valign="top" class="TableCellDark">
<td width="100"></td>
<td>&nbsp;&nbsp;</td>
<td><input type="checkbox" name="indexReceiveBlockBlacklist" align="top" #[indexReceiveBlockBlacklistChecked]#></td>
<td>If checked, your peer silently ignores transmitted URLs that match your blacklist</td>
</tr>
<tr valign="top" class="TableCellLight">
<td></td>
<td><input type="submit" name="setIndexTransmission" value="set"></td>
<td></td>
<td>Changes will take effect immediately</td>
</tr>
</table>
</p>
</form>
#[result]#
#[footer]#
</body>
</html>