In this guide, we describe some of the potential causes that can cause external content to be cleaned up, and then we suggest several possible fixes that you can try to resolve.
Stop wasting time with computer errors.
I wrote a script for about 2GB content store based on custom files
var docs Search = .luceneSearch (“PATH: ” / app: company_home / cm: main // * “AND TYPE: ” doc: somecontent “”);
var paperwork = search.luceneSearch (“PATH: ” / app: company_home / cm: main // * “AND TYPE: ” cm: folder “AND NOT TYPE: ” cm: system folder “AND NOT @cm : name: ” folder1 “AND NOT @cm : name: ” folder2 “AND NOT @cm : name: “folder3 ” ET PAS @cm : name: “folder4 ” AND NOT AND @cm : name: “folder5 ” NOT @cm : name: “folder6 “”);
is for (i = 0; i
The outer instance is almost clean, but the content store in the file system is clearly a constant 2 GB.
How convenient is it to remove unused content from an archive file on the system?
To ensure the correct functioning of the Alfresco server, all you need to do is perform regular server maintenance (cleaning the server). The frequency of servicing depends on how documents are almost always updated and how more and more documents are published on a computer on the Internet. This section shows how the currentAlfresco cleans up the server manually using the command line interface. For instructions on performing an automatic cleanup, see Automatically cleaning Alfresco server .
- PostgreSQL cleanup
Clean Up PostgreSQL
Before starting to clean up PostgreSQL, make sure Alfresco Tomcat server is up and running and Alfresco PostgreSQL is running as described below.
Alfresco server manager dialog.
- Be sure to open the command line interface.
- Connect to the database using the following steps:
- Using the command line, change to the cd /
/ installation postgresql / bin directory.
Run one of the commands immediately after:
For Windows: psql -U alfresco
For Linux: ./psql -U alfresco
- Enter the PostgreSQL end user password. This is usually the same password as the Alfresco administrator password.
- Using the command line, change to the cd /
- Find out which data is taking up the most space by running the following commands:
select type_qname_id, while count (*) cnt alf_node during the year uppas store_id = 6 and also type_qname_id, ordered by cnt desc;
Remember to add a semicolon at the end of the command as shown above.
select 2.from alf_qname qn alf_namespace ns still occurs qn.ns_id = ns.id , where qn.id in (247, 49);
Add 144, your data!
The numbers 247, one hundred forty four, 49 in the command are derived from the results of the previous command. Always choose identifiers with the largest amount of data. In this example, it is 247, one hundred forty four, 49.
The result should look like the following example. Note that in the example, data with ID 144 is marked as deleted. In the picture above, you can see that this is the largest amount of data in this database at the moment (173,050).
Identifiers’ defined the data type may be different for your service.
Determine the time (in milliseconds) of the last transaction that you want to delete from the server following important stepsand:
- Go to https: // www .epochconverter .com /.
In EpochConverter, enter the full date of the last returned transaction to delete it from the server and get the timestamp in milliseconds. For example, if you enter July 17, 2017 (GTM +03: 00), the time stamp will be 1500238800000 milliseconds.
Best practice is directly related to this date before a specific time, to subtract only dates up to a specific week.
Get the ID of the last contract that was removed from the node by running the following command:
select account record from alf_transaction, where commit_time_ms <= 1500238800000 Framework by commit_time_ms desc limit Your 1;
The number 1500238800000 in the whole command is the timestamp value from the example. Before running the command, you must include the example timestamp in your own
The figure below shows the output of a command where the timestamp value is 1500238800000. In this example, the ID of the last tax to be removed from the host is 30841.
Find the number of parts to remove from the host server. is done with the following guide (optional):
select count (id) from alf_node where type_qname_id means 144 and transaction_id <= 30841;
Add all your data!
Replace when property values ‚Äč‚Äčwith your custom data :
type_qname_id matches 144 - lost data ID. <=
trasaction_id 30841 - ID of the last transaction that was just deleted from the server.
In the following example, the amount of data (the amount of deleted data marked as deleted and older than the transaction being deleted) is 176225.
- Delete all data, marked as deleted by running the following commands:
delete from alf_node_prope rties, via node_id in (select id including alf_node, where type_qname_id = 144, then transaction_id <= 30841);
Add your details!
Replace the benefits of the following properties with custom data:
type_qname_id = - 144 any remote data identifier. <=
trasaction_id 30841 ~ ID of the last long transaction to be deleted from a specific server.
This command removes the properties of all specified data nodes.
Remove from alf_node where type_qname_id = 144 and therefore <= Transaction_id 30841;
Add You add your data!
Replace the cost of the following end properties with our custom data:
type_qname_id = 144 is the specific identifier of the deleted data. <=
trasaction_id 30841 1 ID of the current transaction that should be deleted from the server.
This command removes the node assigned to the data.
- Make sure the data is marked as the remote was removed with the following startup command:
select count (*) type_qname_id, for example cnt from alf_node, where store_id = grouped by type_qname_id after cnt desc;
In the example below, you can see that most of the understands marked as deleted (ID 144) seem to be deleted. Data volume increased from 173,050,820.
When you're done cleaning up, move postgresql, which covers the next server maintenance, and do the Solr4 cleanup described in the next section.
Before starting to clean up Solr4, make sure most of Alfresco Server Tomcat and Alfresco PostgreSQL are shut down as shown below.
Alfresco Device Manager dialog box.
- Change to
/ alf_data installation directory.
- Remove the folders in use:
- contentstore. removed
- Go to the project and installation directory
/ alf_data / solr4.
- Delete the folders:
For security reasons, it is recommended that you back up the Alfresco server before making any virtual changes.
Remember to put a semicolon at the end of the command, as shown above.
The numbers 247, 144, 1949 in the command are subtracted from the results of the previous command. Always choose identifiers with our own volume of data. In this example, it is 247, 144, 49.
V In our basic setting, the identifiers for a particular important data type are actually different.
It is best to use a new date from the previous week so that only actual dates older than one week are removed.
Selecting 1500238800000 in the command is sort of an example of a timestamp value. Remember to replace the timestamp in the example with your own
before running your command. replace
The figure below shows the output of a command where the timestamp detection is 1500238800000. In this example, the ID of all recent transactions to be deleted from the server is 30841.
Replace the values ‚Äč‚Äčof the following properties containing your custom data:
type_qname_id = one hundred forty four - identifier of the deleted data. <=
trasaction_id 30841 is the ID of this last specific transaction to be performed on the server received by the remote.
In the example below, that specific amount of data to be deleted (the amount of data marked as deleted and also older than the last transaction to be deleted) is —ā 176225.
Replace the values ‚Äč‚Äčof the following properties with your specific data:
type_qname_id = 144 - the identifier of the deleted data. <=
trasaction_id 30841 - usually the identifier of the last contract that was deleted from this Server.
Replace the stored property values ‚Äč‚Äčwith your custom data:
type_qname_id = one hundred forty-four - the identifier of the deleted data. <=
trasaction_id 30841 - identifier of all recent transactions to be cleared by the server.
Posprzataj Na Swiezym Powietrzu Kontaktujac Sie Z Trescia
Limpeza Ao Ar Livre Contatando O Conteudo
Opruimen Buiten Contact Met Inhoud
Pulizia All Aperto Contattando I Contenuti
Nettoyer En Plein Air Contactant Le Contenu
Stadning Utomhus Kontaktande Innehall
žēľžôł ž†ĎžīČ žĹėŪÖźžł† ž†ēŽ¶¨ ž†ēŽ¶¨
Kontaktaufnahme Mit Inhalten Im Freien Aufraumen
Limpieza Al Aire Libre Contactando Contenido
Ochistka Kontakta S Kontentom Na Otkrytom Vozduhe