Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / apache/druid issues and pull requests

#1709 - Peon OOM causes task to never terminate

Issue - State: open - Opened by drcrallen about 9 years ago - 8 comments
Labels: Bug, Area - Batch Ingestion, Area - Operations, stale

#1709 - Peon OOM causes task to never terminate

Issue - State: open - Opened by drcrallen about 9 years ago - 8 comments
Labels: Bug, Area - Batch Ingestion, Area - Operations, stale

#1709 - Peon OOM causes task to never terminate

Issue - State: open - Opened by drcrallen about 9 years ago - 8 comments
Labels: Bug, Area - Batch Ingestion, Area - Operations, stale

#1709 - Peon OOM causes task to never terminate

Issue - State: open - Opened by drcrallen about 9 years ago - 8 comments
Labels: Bug, Area - Batch Ingestion, Area - Operations, stale

#1709 - Peon OOM causes task to never terminate

Issue - State: open - Opened by drcrallen about 9 years ago - 8 comments
Labels: Bug, Area - Batch Ingestion, Area - Operations, stale

#1709 - Peon OOM causes task to never terminate

Issue - State: open - Opened by drcrallen about 9 years ago - 8 comments
Labels: Bug, Area - Batch Ingestion, Area - Operations, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1615 - [Proposal] : Better handling for *bad* worker nodes.

Issue - State: open - Opened by nishantmonu51 over 9 years ago - 7 comments
Labels: Discuss, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1460 - new task might stay waiting forever if there is a zhombie task lock stored in task_locks table

Issue - State: open - Opened by himanshug over 9 years ago - 1 comment
Labels: Bug, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1440 - Add ability to shutdown historical tier with replication factor 1 without having temporary data outages

Issue - State: open - Opened by drcrallen over 9 years ago - 5 comments
Labels: Area - Querying, Area - Segment Balancing/Coordination, stale

#1415 - Timeout not honored

Issue - State: closed - Opened by drcrallen over 9 years ago - 7 comments
Labels: Bug, Area - Querying, stale

#1415 - Timeout not honored

Issue - State: closed - Opened by drcrallen over 9 years ago - 7 comments
Labels: Bug, Area - Querying, stale

#1415 - Timeout not honored

Issue - State: closed - Opened by drcrallen over 9 years ago - 7 comments
Labels: Bug, Area - Querying, stale

#1415 - Timeout not honored

Issue - State: closed - Opened by drcrallen over 9 years ago - 7 comments
Labels: Bug, Area - Querying, stale

#1415 - Timeout not honored

Issue - State: closed - Opened by drcrallen over 9 years ago - 7 comments
Labels: Bug, Area - Querying, stale

#1341 - SocketUtil.findOpenPort does not always find a desired port correctly for unit tests

Issue - State: open - Opened by drcrallen over 9 years ago - 3 comments
Labels: Bug, Starter, stale

#1341 - SocketUtil.findOpenPort does not always find a desired port correctly for unit tests

Issue - State: open - Opened by drcrallen over 9 years ago - 3 comments
Labels: Bug, Starter, stale

#1341 - SocketUtil.findOpenPort does not always find a desired port correctly for unit tests

Issue - State: open - Opened by drcrallen over 9 years ago - 3 comments
Labels: Bug, Starter, stale

#1341 - SocketUtil.findOpenPort does not always find a desired port correctly for unit tests

Issue - State: open - Opened by drcrallen over 9 years ago - 3 comments
Labels: Bug, Starter, stale

#1341 - SocketUtil.findOpenPort does not always find a desired port correctly for unit tests

Issue - State: open - Opened by drcrallen over 9 years ago - 3 comments
Labels: Bug, Starter, stale

#1341 - SocketUtil.findOpenPort does not always find a desired port correctly for unit tests

Issue - State: open - Opened by drcrallen over 9 years ago - 3 comments
Labels: Bug, Starter, stale

#1341 - SocketUtil.findOpenPort does not always find a desired port correctly for unit tests

Issue - State: open - Opened by drcrallen over 9 years ago - 3 comments
Labels: Bug, Starter, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1291 - Querying for data in newly announced segment (sometimes) gives no results.

Issue - State: open - Opened by KenjiTakahashi over 9 years ago - 7 comments
Labels: Bug, Ease of Use, stale

#1284 - Integration tests should use mixed timezones

Issue - State: open - Opened by fjy over 9 years ago - 1 comment
Labels: Ease of Use, Area - Testing, stale

#1284 - Integration tests should use mixed timezones

Issue - State: open - Opened by fjy over 9 years ago - 1 comment
Labels: Ease of Use, Area - Testing, stale

#1284 - Integration tests should use mixed timezones

Issue - State: open - Opened by fjy over 9 years ago - 1 comment
Labels: Ease of Use, Area - Testing, stale

#1284 - Integration tests should use mixed timezones

Issue - State: open - Opened by fjy over 9 years ago - 1 comment
Labels: Ease of Use, Area - Testing, stale

#1284 - Integration tests should use mixed timezones

Issue - State: open - Opened by fjy over 9 years ago - 1 comment
Labels: Ease of Use, Area - Testing, stale

#1263 - Support for etcd and consul

Issue - State: open - Opened by F21 over 9 years ago - 9 comments
Labels: Feature, Ease of Use, stale

#1263 - Support for etcd and consul

Issue - State: open - Opened by F21 over 9 years ago - 9 comments
Labels: Feature, Ease of Use, stale

#1147 - Hadoop tasks can write out zero-byte files and complete "successfully"

Issue - State: open - Opened by gianm almost 10 years ago - 1 comment
Labels: Bug, stale

#1147 - Hadoop tasks can write out zero-byte files and complete "successfully"

Issue - State: open - Opened by gianm almost 10 years ago - 1 comment
Labels: Bug, stale

#1147 - Hadoop tasks can write out zero-byte files and complete "successfully"

Issue - State: open - Opened by gianm almost 10 years ago - 1 comment
Labels: Bug, stale

#1147 - Hadoop tasks can write out zero-byte files and complete "successfully"

Issue - State: open - Opened by gianm almost 10 years ago - 1 comment
Labels: Bug, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1078 - Remove ColumnConfig from IndexIO and move column lookup caching decision into query adapter

Issue - State: open - Opened by xvrl almost 10 years ago - 4 comments
Labels: Feature, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1036 - Query Data Source - Aggregator Issue

Issue - State: open - Opened by basdag almost 10 years ago - 2 comments
Labels: Bug, Area - Querying, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale

#1023 - The logic on the coordinator to find segments to merge is inefficient

Issue - State: open - Opened by fjy almost 10 years ago - 1 comment
Labels: Bug, Performance, Area - Segment Balancing/Coordination, stale