You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gsoc@community.apache.org by "Maxim Solodovnik (Jira)" <ji...@apache.org> on 2026/03/21 04:55:00 UTC
[jira] [Commented] (GSOC-332) Instance-Aware Platform Registration and Optimization
[ https://issues.apache.org/jira/browse/GSOC-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18067221#comment-18067221 ]
Maxim Solodovnik commented on GSOC-332:
---------------------------------------
It seems Wayang has their own Jira: https://issues.apache.org/jira/projects/WAYANG/issues/WAYANG-16?filter=allopenissues
I wonder why it wasn't used?
> Instance-Aware Platform Registration and Optimization
> -----------------------------------------------------
>
> Key: GSOC-332
> URL: https://issues.apache.org/jira/browse/GSOC-332
> Project: Comdev GSOC
> Issue Type: New Feature
> Reporter: Zoi Kaoudi
> Priority: Major
> Labels: Wayang, gsoc, gsoc2026, mentor
>
> *Background:*
> Apache Wayang is a cross-platform data processing framework that enables users to execute analytics pipelines across multiple execution engines. Currently, Wayang’s architecture is "platform-type centric," treating each technology (e.g., Spark, Flink, or RDBMS) as a single global entity.
> In modern distributed environments, resources are often partitioned across multiple instances of the same technology—such as separate database clusters for different regions or compute clusters with varying hardware profiles. Currently, Wayang cannot natively distinguish between these instances, preventing the optimizer from routing tasks based on specific instance metadata or data proximity.
> *Project Goal:*
> The objective is to evolve Wayang from a "type-based" registration model to an instance-aware model. This allows Wayang to manage and differentiate between multiple deployments of the same execution engine within a single session.
> *Key Objectives:*
> Identity & Registration: Enhance the core registration service to support unique instance identifiers, allowing multiple deployments of the same platform type to coexist.
> Scoped Configuration: Implement a hierarchical configuration mechanism to tie parameters (connection strings, resource limits, performance weights) to specific instance IDs.
> Optimization Granularity: Update the cost-estimation logic to recognize these distinct instances, enabling the optimizer to make informed decisions based on the specific characteristics of individual backends.
>
> {*}Difficulty{*}: Medium
> {*}Project size{*}: 375 hours (Large)
>
> *Potential mentors:*
> * Haralampos (Harry) Gavriilidis — harryg (at) apache.org
> * Zoi Kaoudi
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: gsoc-unsubscribe@community.apache.org
For additional commands, e-mail: gsoc-help@community.apache.org