log.go:34] Got compaction priority: {level:0 score:1 dropPrefix:[]}
log.go:34] Running for level: 0
```
I waited for hours but it still didn’t work. I stopped and restarted Alpha, but it still continues to process
I stop the services and delete the Alpha and Zero folder and its data and import the export I got and the problem is fixed, but a few hours later the same problem is repeated again.
I have used different versions, but the same error is repeated
versions :
1.2.3
1.2.6
2.03.3
20.03.6
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [November 11, 2020, 6:05pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/2 "2020-11-11T18:05:57Z")
There’s no issue in your logs. You can ignore those processes. The abort task is a background task that will always run. Besides this, are you getting something else?
---
### Author:  [@javadnasrollahi](https://discuss.dgraph.io/u/javadnasrollahi)
#### Post date: [November 11, 2020, 6:12pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/3 "2020-11-11T18:12:38Z")
Hi @MichelDiz
thanks for your answer
But the process is such that dgraph do not respond to any request. Neither to ratel nor to the golang client
After many hours, the problem still does not go away
In some cases, the use of RAM increases so much that the consumption of RAM reaches a maximum and the dgraph crashes.
Also, dgraph starts generating files in the alpha folder, so that in some cases a 30 GB file is generated in less than 30 minutes.
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [November 11, 2020, 6:17pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/4 "2020-11-11T18:17:10Z")
What are you doing? loading massive data?
---
### Author:  [@javadnasrollahi](https://discuss.dgraph.io/u/javadnasrollahi)
#### Post date: [November 11, 2020, 6:22pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/5 "2020-11-11T18:22:49Z")
No
We have an educational site with 2,000 users
In our site, educational processes are followed, including tests, assignments, meetings, etc.
Within hours of the day, the number of database transactions reaches 100 per second
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [November 11, 2020, 6:24pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/6 "2020-11-11T18:24:13Z")
What is your deploy implementation? docker? bare metal? k8s?
Also, what are the specs?
---
### Author:  [@javadnasrollahi](https://discuss.dgraph.io/u/javadnasrollahi)
#### Post date: [November 11, 2020, 6:28pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/7 "2020-11-11T18:28:16Z")
It is written with golang
use this packages in my dg client
```auto
"github.com/dgraph-io/dgo/v2"
"github.com/dgraph-io/dgo/v2/protos/api"
grpc "google.golang.org/grpc"
```
zero service config:
```auto
{
"my": "localhost:5080",
"wal": "/db/z0/zw"
}
```
and alpha service conf:
```auto
{
"my": "localhost:7080",
"zero": "localhost:5080",
"lru_mb": 2048,
"postings": "/db/a0/p",
"wal": "/db/a0/w"
}
```
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [November 11, 2020, 6:31pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/8 "2020-11-11T18:31:01Z")
But are you using docker? bare metal? k8s? what are the specifications of those machines?
If you don’t wanna have issues with Dgraph day to day administration you can use the hosted service Slash [https://dgraph.io/slash-graphql](https://dgraph.io/slash-graphql) - it can forward the DQL GRPC service for you.
---
### Author:  [@javadnasrollahi](https://discuss.dgraph.io/u/javadnasrollahi)
#### Post date: [November 11, 2020, 6:36pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/9 "2020-11-11T18:36:42Z")
I work on ubuntu 18.04 server
the specifications of those machines:
CPU: 6Core
Ram: 24G
---
### Author:  [@javadnasrollahi](https://discuss.dgraph.io/u/javadnasrollahi)
#### Post date: [November 11, 2020, 6:39pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/10 "2020-11-11T18:39:53Z")
> [@MichelDiz](#):
>
> But are you using docker? bare metal? k8s?
What do you mean by that? “But are you using docker? bare metal? k8s?”
Ii used Automatic download according to:
> **[Overview - Dgraph](https://docs.hypermode.com/dgraph/overview)**
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [November 11, 2020, 6:44pm UTC](https://discuss.dgraph.io/t/found-1-old-transactions-acting-to-abort-them/11420/11 "2020-11-11T18:44:37Z")
So you have a bare metal machine running Dgraph binary?
1. Move to the latest version of Dgraph.
2. Remove the lru\_mb option value. (optional)
3. If you have multiple hard disks you could setup multiple Alphas and each one could use a disk/SSD.
Multiple Alphas are good to spread the load among the cluster.
1. You can use best-effort queries [https://dgraph.io/docs/clients/raw-http/#running-best-effort-queries](https://dgraph.io/docs/clients/raw-http/#running-best-effort-queries) and best-effort queries [RAFT - Design concepts](https://dgraph.io/docs/design-concepts/raft/#read-only-queries)
> [@javadnasrollahi](#):
>
> Ii used Automatic download according to:
> [https://dgraph.io/docs/deploy/download/#automatic-download](https://dgraph.io/docs/deploy/download/#automatic-download)
I see, it is really a bare-metal machine.