简体   繁体   English

必须配置路径“enqueue_elastica”处的子节点“transport”

[英]The child node "transport" at path "enqueue_elastica" must be configured

In a Symfony 4.3 app with friendsofsymfony/elastica-bundle 5.1.0, enqueue/elastica-bundle 0.9.3, and enqueue/fs 0.9.12 installation of the latter ends with:在带有friendsofsymfony/elastica-bundle 5.1.0、 enqueue/elastica-bundle 0.9.3和enqueue/fs 0.9.12的Symfony 4.3应用程序中,后者的安装结束于:

The child node "transport" at path "enqueue_elastica" must be configured.必须配置路径“enqueue_elastica”处的子节点“transport”。

I've tried multiple permutations in enqueue.yaml , including the only example I've found.我在enqueue.yaml尝试了多种排列,包括我找到的唯一示例

enqueue.yaml:入队.yaml:

enqueue:
    default:
        transport: '%env(resolve:ENQUEUE_DSN)%'
        client: ~

.env includes: .env 包括:

###> enqueue/enqueue-bundle ###
ENQUEUE_DSN=null://
###< enqueue/enqueue-bundle 

Elasticsearch 6.8 is installed. Elasticsearch 6.8 已安装。 Relatively simple indexes are readily created.相对简单的索引很容易创建。 A more complex index fails with running out of memory - thus the need for enqueue .更复杂的索引因内存不足而失败 - 因此需要enqueue

What is an appropriate configuration of enqueue.yaml for filesystem transport?用于文件系统传输的enqueue.yaml的适当配置是什么?

Edit: Curiously, the Ubuntu 18 Hyper-V virtual machine was able to slog through the populating without enqueue while the Windows host failed at 94200/156865.编辑:奇怪的是,当 Windows 主机在 94200/156865 失败时,Ubuntu 18 Hyper-V 虚拟机能够在没有enqueue的情况下进行填充。

The seemingly correct config has:看似正确的配置有:

.env: .env:

...
###> enqueue/enqueue-bundle ###
ENQUEUE_DSN="file://%VAR_DIR%/enqueue"
###< enqueue/enqueue-bundle ###

This needed to accompanied by这需要伴随

enqueue.yaml:入队.yaml:

enqueue:
    default:
        transport:
            dsn: '%env(resolve:ENQUEUE_DSN)%'
            path: '%kernel.project_dir%/var/queue' ## probably just a placeholder
        client: ~

While the above avoids any errors being thrown it does not allow the populating to complete.虽然上述避免了抛出任何错误,但它不允许填充完成。 I'm officially stuck.我被正式卡住了。 Time to look at reducing index complexity and multi index searches.是时候考虑降低索引复杂性和多索引搜索了。

You should add你应该添加

enqueue_elastica:
    transport: '%enqueue.default_transport%'
    doctrine: ~

In your enqueue.yaml config在你的enqueue.yaml配置中

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 FOSOAuthServerBundle-必须配置路径“ security”处的子节点“ providers” - FOSOAuthServerBundle - The child node “providers” at path “security” must be configured 必须配置路径“security.firewalls.main.remember_me”中的子节点“secret” - The child node “secret” at path “security.firewalls.main.remember_me” must be configured FOSUser Bundle必须配置路径“fos_user”中的子节点“db_driver” - FOSUser Bundle The child node “db_driver” at path “fos_user” must be configured 必须配置路径“ hwi_oauth”中的子节点“ resource_owners” - The child node “resource_owners” at path “hwi_oauth” must be configured Symfony 4-必须配置路径“ beelab_tag”上的子节点“ tag_class” - Symfony 4 - The child node “tag_class” at path “beelab_tag” must be configured 停滞的RedKiteCMS安装:“必须配置路径“ fos_user”处的子节点“ db_driver” - Stalled RedKiteCMS install: “The child node ”db_driver“ at path ”fos_user“ must be configured” 无法将脚本排入子主题 - Unable to Enqueue Scripts in Child Theme 必须配置路径“ewz_recaptcha”处的 Symfony 4 Recaptcha 包“public_key” - Symfony 4 Recaptcha bundle "public_key" at path "ewz_recaptcha" must be configured 获取到(父/子)数组父节点的路径 - Get path to parent node of (parent/child) array WordPress子主题中错误的入队脚本顺序 - wrong enqueue script order in wordpress child theme
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM