content/operate/oss_and_stack/stack-with-enterprise/search/search-active-active.md
Starting with RediSearch 2.x, supported in Redis Software (RS) 6.0 and later, you can [enable search and query]({{< relref "/operate/oss_and_stack/stack-with-enterprise/install/add-module-to-database" >}}) for [Active-Active databases]({{< relref "/operate/rs/databases/active-active" >}}) at the time of creation.
You can run search operations on any instance of an Active-Active database.
Active-Active databases do not support the following search and query commands:
FT.DROPINDEX ]({{< relref "commands/ft.dropindex" >}})FT.SUGADD]({{< relref "commands/ft.sugadd" >}})FT.SUGGET]({{< relref "commands/ft.sugget" >}})FT.SUGDEL]({{< relref "commands/ft.sugdel" >}})FT.SUGLEN]({{< relref "commands/ft.suglen" >}})Here's an example to help visualize Active-Active search and query:
| Time | Description | CRDB Instance1 | RediSearch Instance 1 | CRDB Instance 2 | RediSearch Instance 2 |
|---|---|---|---|---|---|
| t0 | Create the index on each instance | FT.CREATE idx .... | FT.CREATE idx .... | ||
| t1 | Add doc1 as a hash on instance 1; RediSearch indexes doc1 on instance 1 | HSET doc1 field1 "a" | (Index doc1 field1 "a") | ||
| t2 | Add doc2 as a hash on instance 2; RediSearch indexes doc2 on instance 2 | HSET doc1 field2 "b" | (Index doc1 field2 "b") | ||
| t3 | Searching for "a" in each instance only finds the result in instance 1 | FT.Search idx "a" |
The practical result is that you have a geo-distributed database with a high level of consistency that can also run search operations on any instance.