----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72453/ -----------------------------------------------------------
Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nikhil Bonte, and Sarath Subramanian. Repository: atlas Description ------- Inconsistency in search result is seen when atlas.graph.index.search.max-result-set-size is set lower to max result size when solr replication factor is 2. To overcome this issue set default value "2147483647" for "atlas.graph.index.search.max-result-set-size" property in Atlas ApplicationProperties. Diffs ----- intg/src/main/java/org/apache/atlas/ApplicationProperties.java 1f1f3771b Diff: https://reviews.apache.org/r/72453/diff/1/ Testing ------- PC build :- https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1857/console Scenario - 1 When atlas-application.properties is set with atlas.graph.index.search.max-result-set-size=200 [inconsistency seen in search result ] 2020-04-29 18:10:39,799 INFO - [main:] ~ Loading atlas-application.properties from file:/usr/hdp/current/atlas-server/conf/atlas-application.properties (ApplicationProperties:133) 2020-04-29 18:10:39,809 INFO - [main:] ~ Using graphdb backend 'janus' (ApplicationProperties:285) 2020-04-29 18:10:39,809 INFO - [main:] ~ Using storage backend 'hbase2' (ApplicationProperties:296) 2020-04-29 18:10:39,809 INFO - [main:] ~ Using index backend 'solr' (ApplicationProperties:307) 2020-04-29 18:10:39,809 INFO - [main:] ~ Atlas is running in MODE: PROD. (ApplicationProperties:311) 2020-04-29 18:10:39,810 INFO - [main:] ~ Setting solr-wait-searcher property 'true' (ApplicationProperties:317) 2020-04-29 18:10:39,810 INFO - [main:] ~ Setting index.search.map-name property 'false' (ApplicationProperties:321) 2020-04-29 18:10:39,810 INFO - [main:] ~ Setting atlas.graph.index.search.max-result-set-size = 200 (ApplicationProperties:331)(ApplicationProperties:343) ---------------------------------------------------------------------------------------------------------------------------- Scenario 2 - When custom property atlas.graph.index.search.max-result-set-size is removed from Ambari [ search results are consistent in size] 2020-04-29 18:17:01,883 INFO - [main:] ~ Loading atlas-application.properties from file:/usr/hdp/current/atlas-server/conf/atlas-application.properties (ApplicationProperties:133) 2020-04-29 18:17:01,892 INFO - [main:] ~ Using graphdb backend 'janus' (ApplicationProperties:285) 2020-04-29 18:17:01,892 INFO - [main:] ~ Using storage backend 'hbase2' (ApplicationProperties:296) 2020-04-29 18:17:01,892 INFO - [main:] ~ Using index backend 'solr' (ApplicationProperties:307) 2020-04-29 18:17:01,893 INFO - [main:] ~ Atlas is running in MODE: PROD. (ApplicationProperties:311) 2020-04-29 18:17:01,893 INFO - [main:] ~ Setting solr-wait-searcher property 'true' (ApplicationProperties:317) 2020-04-29 18:17:01,893 INFO - [main:] ~ Setting index.search.map-name property 'false' (ApplicationProperties:321) 2020-04-29 18:17:01,893 INFO - [main:] ~ Setting atlas.graph.index.search.max-result-set-size = 2147483647 (ApplicationProperties:331)2020-04-29 18:17:01,893 INFO - [main:] ~ Property (set to default) atlas.graph.cache.db-cache = true (ApplicationProperties:343) Thanks, Nixon Rodrigues